From owner-freebsd-current Sun Sep 29 13:23: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4622637B401; Sun, 29 Sep 2002 13:23:00 -0700 (PDT) Received: from mail44.fg.online.no (mail44-s.fg.online.no [148.122.161.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85F8F43E42; Sun, 29 Sep 2002 13:22:58 -0700 (PDT) (envelope-from frode@nordahl.net) Received: from samwise (ti200720a080-0824.bb.online.no [80.212.247.56]) by mail44.fg.online.no (8.9.3/8.9.3) with ESMTP id WAA03730; Sun, 29 Sep 2002 22:22:55 +0200 (MEST) Subject: Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernel over the weekend?) From: Frode Nordahl To: Eric Anholt Cc: Wesley Morgan , Maxim Sobolev , walt , freebsd-current@FreeBSD.org In-Reply-To: <1033327093.873.11.camel@anholt.dyndns.org> References: <20020929132405.Q3750-100000@volatile.chemikals.org> <1033327093.873.11.camel@anholt.dyndns.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 29 Sep 2002 22:22:53 +0200 Message-Id: <1033330975.615.41.camel@samwise.xu.nordahl.net> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 > 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