From owner-freebsd-current Thu Jan 30 8:57:45 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87C3C37B401 for ; Thu, 30 Jan 2003 08:57:44 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECF8643F75 for ; Thu, 30 Jan 2003 08:57:43 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.6/8.12.5) with SMTP id h0UGvZP4026002; Thu, 30 Jan 2003 11:57:35 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 30 Jan 2003 11:57:35 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Craig Dooley Cc: freebsd-current@freebsd.org Subject: Re: Recent current dies hard with simple program In-Reply-To: <20030130164658.GA9063@xlnx-x.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 30 Jan 2003, Craig Dooley wrote: > Last cvsup/world/kernel is from around midnight last night, but noticed > the problem yesterday. For a csi class I have to sort and uniq a file > in c, and as a test case, I wrote a simple hex dump that respects > newlines. No matter what I give it as input, it will hard crash the > system. No DDB, no panic, just hard locked. When trying to run it > under GDB, break on main, as soon as I type run, it dies again. Im > writing it on the same machine with much more significant programs > running absolutely perfectly. I'm attaching the source to see if it's a > common problem with anyone else. > > FreeBSD broken.xlnx-x.net 5.0-CURRENT FreeBSD 5.0-CURRENT #8: Thu Jan 30 > 01:01:45 EST 2003 craig@broken.xlnx-x.net:/usr/obj/usr/src/sys/BROKEN > i386 Doesn't happen here with a kernel from the 28th. I tried a couple of input files without luck. Sometimes, it's easier to get into DDB if you're using a serial console and serial break -- could you try that? When the system is stuck in a tight spin while holding Giant, for example, the console debugger may not be able to generate a useful break. This will improve if we can get the system console to get less involved in Giant. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message