From owner-freebsd-current Sun Jan 5 2:47: 0 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 45E2937B401; Sun, 5 Jan 2003 02:46:59 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04C1743EA9; Sun, 5 Jan 2003 02:46:57 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA27650; Sun, 5 Jan 2003 21:46:53 +1100 Date: Sun, 5 Jan 2003 21:47:11 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Robert Watson Cc: current@FreeBSD.ORG, Subject: Re: pthread ^T problem on recent -CURRENT: death in libc_r mutex In-Reply-To: Message-ID: <20030105212512.A330-100000@gamplex.bde.org> 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 Sat, 4 Jan 2003, Robert Watson wrote: > Juli Mallett pointed me at the following reproduceable problem on my > -current notebook with userland/kernel dated Dec 29: > > paprika:~/freebsd/test/pthread> ./test > ... > load: 0.23 cmd: test 914 [running] 0.00u 0.01s 0% 824k > 1 > Bus error (core dumped) > > Hitting ^T to get status information seems to break output following the > first printf after the information display. Here's the stack trace from > the test program from the first execution above: This caused a reproducible kernel panic for a null pointer bug in ttyinfo() here, but seemed to work right once I fixed the panic. (The panic was just a bug in my unbreaking of the calculation of rss.) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message