From owner-freebsd-bugs Fri Feb 24 12:11:22 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA23650 for bugs-outgoing; Fri, 24 Feb 1995 12:11:22 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA23643 for ; Fri, 24 Feb 1995 12:11:21 -0800 Received: from geli.clusternet (rcarter.vip.best.com [204.156.137.2]) by shell1.best.com (8.6.9/8.6.5) with ESMTP id MAA03574 for ; Fri, 24 Feb 1995 12:10:24 -0800 Received: (from rcarter@localhost) by geli.clusternet (8.6.9/8.6.9) id MAA00484 for freebsd-bugs@freebsd.org; Fri, 24 Feb 1995 12:09:29 -0800 Date: Fri, 24 Feb 1995 12:09:29 -0800 From: "Russell L. Carter" Message-Id: <199502242009.MAA00484@geli.clusternet> To: freebsd-bugs@FreeBSD.org Subject: gdb crashes fixed? *ouch* Sender: bugs-owner@FreeBSD.org Precedence: bulk Looks like I've run into the gdb bug in a 021095 system. Without gdb I'm dead in the water, but if I go back too far I end up with a lot of grief from this ncr problem, which intermittently crashes the system, too: snippet from dmesg: assertion "cp == np->header.cp" failed: file "../../pci/ncr.c", line 5454 assertion "cp" failed: file "../../pci/ncr.c", line 5455 sd0(ncr0:1:0): COMMAND FAILED (4 28) @f0992a00. sd0(ncr0:1:0): NOT READY asc:04 ascq:01, retries:4 sd0(ncr0:1:0): NOT READY asc:04 ascq:01, retries:4 sd0(ncr0:1:0): NOT READY asc:04 ascq:01, retries:4 sd0(ncr0:1:0): NOT READY asc:04 ascq:01, retries:3 sd0(ncr0:1:0): NOT READY asc:04 ascq:01, retries:3 sd0(ncr0:1:0): NOT READY asc:04 ascq:01, retries:3 sd0(ncr0:1:0): NOT READY asc:04 ascq:01, retries:2 that stuff is regularly showing up in an earlier dated system which doesn't have the gdb crash bug. Has the gdb crash problem been fixed recently? Is there someway to figure that out without having to email the list? practicing steady breathing, Russell