From owner-freebsd-current Sun Sep 29 13:26: 9 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 1B51C37B401; Sun, 29 Sep 2002 13:26:08 -0700 (PDT) Received: from volatile.chemikals.org (cae57-176-131.sc.rr.com [66.57.176.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E7FF43E75; Sun, 29 Sep 2002 13:26:07 -0700 (PDT) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.12.5/8.12.5) with ESMTP id g8TKPxQU004981; Sun, 29 Sep 2002 16:25:59 -0400 (EDT) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost) by volatile.chemikals.org (8.12.6/8.12.6/Submit) with ESMTP id g8TKPw0D004978; Sun, 29 Sep 2002 16:25:59 -0400 (EDT) X-Authentication-Warning: volatile.chemikals.org: morganw owned process doing -bs Date: Sun, 29 Sep 2002 16:25:58 -0400 (EDT) From: Wesley Morgan To: Frode Nordahl Cc: Eric Anholt , Maxim Sobolev , walt , Subject: Re: XFree86 crash, Bezier thing (was Re: Is phk rewriting the kernel over the weekend?) In-Reply-To: <1033330975.615.41.camel@samwise.xu.nordahl.net> Message-ID: <20020929162442.N4827-100000@volatile.chemikals.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Yes, i don't see any -stable systems bombing out. But it _always_ occurrs when typing. No matter what app... Sometimes in the linux opera, sometimes in the konq address bar. I dont think it ever happened when typing in an Xterm though. On 29 Sep 2002, Frode Nordahl wrote: > 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 > -- _ __ ___ ____ ___ ___ ___ Wesley N Morgan _ __ ___ | _ ) __| \ morganw@chemikals.org _ __ | _ \._ \ |) | FreeBSD: The Power To Serve _ |___/___/___/ Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message