From owner-freebsd-current  Sun May  6 21:45:32 2001
Delivered-To: freebsd-current@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id B827837B422
	for <current@FreeBSD.ORG>; Sun,  6 May 2001 21:45:29 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from beppo (beppo [192.67.166.79])
	by feral.com (8.9.3/8.9.3) with ESMTP id VAA16766;
	Sun, 6 May 2001 21:45:26 -0700
Date: Sun, 6 May 2001 21:45:25 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Dag-Erling Smorgrav <des@ofug.org>
Cc: current@FreeBSD.ORG
Subject: Re: lock order reversals, anyone?
In-Reply-To: <xzpoft5j0ou.fsf@flood.ping.uio.no>
Message-ID: <Pine.BSF.4.21.0105062145180.17018-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Possible.

On 7 May 2001, Dag-Erling Smorgrav wrote:

> Matthew Jacob <mjacob@feral.com> writes:
> > > pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped)
> > (oh, yeah, a 4.1 built executable is dying, charming)
> 
> That may well be a bug in your app.  Xscreensaver, for instance, is
> riddled with dangling-pointer and off-by-one bugs that rarely (if
> ever) show up on -STABLE, but result in an immediate core dump on
> -CURRENT because it has malloc() debugging enabled by default.
> 
> DES
> -- 
> Dag-Erling Smorgrav - des@ofug.org
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message