Date: 29 Sep 2002 22:22:53 +0200 From: Frode Nordahl <frode@nordahl.net> To: Eric Anholt <anholt@FreeBSD.org> Cc: Wesley Morgan <morganw@chemikals.org>, Maxim Sobolev <sobomax@FreeBSD.org>, walt <wa1ter@hotmail.com>, freebsd-current@FreeBSD.org Subject: Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernel over the weekend?) Message-ID: <1033330975.615.41.camel@samwise.xu.nordahl.net> In-Reply-To: <1033327093.873.11.camel@anholt.dyndns.org> References: <20020929132405.Q3750-100000@volatile.chemikals.org> <1033327093.873.11.camel@anholt.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2002-09-29 at 21:17, Eric Anholt wrote: > >From what I had heard on the lists it was only a thing that happened > when people upgraded kernels, and that it had stopped after some date of > kernel. I hadn't experienced it, so I ignored it. I don't know about > that link posted, I thought that was a mozilla bug that was supposed to > be fixed. It seems like the bug has been present in XFree86 all the time. But some thing has changed in CURRENT that tickles this bug. I started to experience this after I removed all ports and recompiled XFree86 with the new GCC 3.2.1. X also dies with signal 11 some times, so theres more to it than the Bezier bug. But if it is a CURRENT kernel or compiler issue, I don't understand why / how this should affect -STABLE / -RELEASE. I'll take a backup of my current X installation and do some tests and comparisons against the Aug 24 port build of XFree86. I'll have to find a sure way to reproduce the abort() and / or SIGSEGV failure first though. > -- > Eric Anholt <eta@lclark.edu> > http://people.freebsd.org/~anholt/dri/ > -- Mvh, Frode Nordahl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1033330975.615.41.camel>