Date: Fri, 18 Aug 2006 17:00:25 -0400 From: John Baldwin <jhb@freebsd.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: amd64@freebsd.org Subject: Re: linux32 breakage in current.. Message-ID: <200608181700.25539.jhb@freebsd.org> In-Reply-To: <20060816175424.GA1231@troutmask.apl.washington.edu> References: <200608151701.46724.jhb@freebsd.org> <20060816000424.GA905@troutmask.apl.washington.edu> <20060816175424.GA1231@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 16 August 2006 13:54, Steve Kargl wrote: > 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. Ok. Can you walk it back further? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200608181700.25539.jhb>