Date: Wed, 16 Aug 2006 10:54:24 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: John Baldwin <jhb@freebsd.org> Cc: amd64@freebsd.org Subject: Re: linux32 breakage in current.. Message-ID: <20060816175424.GA1231@troutmask.apl.washington.edu> In-Reply-To: <20060816000424.GA905@troutmask.apl.washington.edu> References: <200608151701.46724.jhb@freebsd.org> <20060815212415.GA1393@troutmask.apl.washington.edu> <20060816000424.GA905@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 15, 2006 at 05:04:24PM -0700, Steve Kargl wrote: > > Oh crap, this is more complicated than I thought > With a kernel built from 2006.08.06.12.00.00 sources, > I'm seeing the classic race condition for locking > > troutmask:kargl[201] acroread church.pdf > Segmentation fault (core dumped) > troutmask:kargl[202] acroread church.pdf <-- This one worked. > troutmask:kargl[203] acroread church.pdf > Segmentation fault (core dumped) > troutmask:kargl[204] acroread church.pdf > Segmentation fault (core dumped) > troutmask:kargl[205] acroread church.pdf <-- This one worked. > troutmask:kargl[206] > > I'll see if I can dig deeper. > The problem appears as early as 01 Aug 06 sources. Out of 16 attempts to run acroread, 5 die with a segfault. It is actually the linux version of bash that drops core. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060816175424.GA1231>