[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: linux32 breakage in current..
- To: Steve Kargl <sgk_(_at_)_troutmask_(_dot_)_apl_(_dot_)_washington_(_dot_)_edu>
- Subject: Re: linux32 breakage in current..
- From: John Baldwin <jhb_(_at_)_freebsd_(_dot_)_org>
- Date: Mon, 21 Aug 2006 13:09:40 -0400
- Cc: amd64_(_at_)_freebsd_(_dot_)_org
On Friday 18 August 2006 18:36, Steve Kargl wrote:
> On Fri, Aug 18, 2006 at 05:00:25PM -0400, John Baldwin wrote:
> > 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?
> >
>
> I've gone as far back as 15 Jul 06, and the problem is still
> there. I ran out of time to go back to earlier versions. I'll
> try again on Monday.
Wow, thanks!
--
John Baldwin
_______________________________________________
freebsd-amd64_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org