Date: Sun, 14 Mar 2010 14:44:21 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Peter Jeremy <peterjeremy@acm.org> Cc: freebsd-x11@freebsd.org, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: X11 crash on exit Message-ID: <4B9D58B5.4050002@freebsd.org> In-Reply-To: <20100314195622.GA88471@server.vk2pj.dyndns.org> References: <4B989064.5030105@freebsd.org> <7d6fde3d1003102245l41ab8287r81680aa40281d802@mail.gmail.com> <4B9C9885.5040601@freebsd.org> <20100314195622.GA88471@server.vk2pj.dyndns.org>
index | next in thread | previous in thread | raw e-mail
Peter Jeremy wrote: > On 2010-Mar-14 00:04:21 -0800, Tim Kientzle <kientzle@freebsd.org> wrote: >> Okay, I've updated a bunch of ports and am still seeing the >> crash. I rebuilt the server with debug symbols and finally >> got something informative; here's the relevant portion of >> the backtrace (frame #10 is the signal 11 delivery). >> >> #11 0x0819e363 in DeliverPropertyEvent (pWin=0x5a5a5a5a, >> value=0xbfbfec0c) at rrproperty.c:34 >> #12 0x0807015d in TraverseTree (pWin=0x28775f80, func=0x819e340 >> <DeliverPropertyEvent>, data=0xbfbfec0c) at window.c:234 .... >> #18 0x0806f4e3 in FreeAllResources () at resource.c:824 >> #19 0x0806bbf0 in main (argc=4, argv=0xbfbfed68, envp=0xbfbfed7c) at >> main.c:411 > > This looks identical to the problem I reported as ports/131930. > Whilst my patch wasn't applied, ISTR a similar patch got applied > upstream to fix the issue. I've run through portsnap/portupgrade a few times, so my server should be up-to-date and I still see the crash. I suspect the upstream patch you're referring to would be the memset(WindowTable, 0, sizeof()) that appears a few lines after the call that triggers the crash. > Other than that, I can confirm that you _can_ run X on an AA1, > at least on 8.x (that's what I'm currently using). What window manager are you using? Right now, I'm using TWM but suspect there's something a bit better suited to this small screen. (Ideally, something that adapts well to either the built-in screen or the external 20" monitor I often use.) > Are you using hal/dbus? Yes. I implemented the fix I suggested earlier (scanning the WindowTable to remove Window objects as they're deleted) and it does consistently resolve the crash, but now the X server restarts itself when xinit asks it to exit, so there's clearly still something amiss. Patch attached for anyone interested. Timhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B9D58B5.4050002>