From owner-freebsd-hackers Mon Mar 2 11:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22816 for freebsd-hackers-outgoing; Mon, 2 Mar 1998 11:01:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22802 for ; Mon, 2 Mar 1998 11:01:36 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA01759; Mon, 2 Mar 1998 10:53:44 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd001757; Mon Mar 2 10:53:41 1998 Message-ID: <34FAFF3B.15FB7483@whistle.com> Date: Mon, 02 Mar 1998 10:49:31 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Mike Smith CC: Greg Lehey , FreeBSD Hackers Subject: Re: Kernel debugging: what's going on here? References: <199802280214.SAA00165@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG M > Whoops. OK, are we sure that "bp" points to the same type in both > cases? And more importantly, that bp->b_vp is expected to be the same > type? (Yes, this is *really* clutching at straws). There's not much > else short of a GDB bug that I can think of that would cause this. > many interrupts are still running.. the clock is still ticking.. I've seen a machine in DDB respond to pings. how are you allocating the new buffer? it looks like it got BZERO'd between the two.. did the malloc actually succeed? etc.etc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message