From owner-freebsd-x11@FreeBSD.ORG Fri Jun 14 14:22:44 2013 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 74D5DD1F for ; Fri, 14 Jun 2013 14:22:44 +0000 (UTC) (envelope-from tmueller@sysgo.com) Received: from mail1.sysgo.com (mail1.sysgo.com [176.9.26.183]) by mx1.freebsd.org (Postfix) with ESMTP id 37D771204 for ; Fri, 14 Jun 2013 14:22:43 +0000 (UTC) Received: from lantia.sysgo.com (unknown [172.22.2.7]) by mail1.sysgo.com (Postfix) with ESMTP id B1E5146170; Fri, 14 Jun 2013 16:13:52 +0200 (CEST) Received: by lantia.sysgo.com (Postfix, from userid 113) id 96E39506085; Fri, 14 Jun 2013 16:13:52 +0200 (CEST) Received: from tmu.ulm.sysgo.com (tmu.ulm.sysgo.com [172.30.3.10]) by lantia.sysgo.com (Postfix) with ESMTP id 543E3506082; Fri, 14 Jun 2013 16:13:52 +0200 (CEST) Date: Fri, 14 Jun 2013 16:13:52 +0200 From: Thomas Mueller To: David Wolfskill Subject: Re: Help debugging xfig lockup? Message-ID: <20130614161352.6b0bdd2d@tmu.ulm.sysgo.com> In-Reply-To: <20130612205800.GA1369@albert.catwhisker.org> References: <20130612045919.GA1940@over-yonder.net> <20130612205800.GA1369@albert.catwhisker.org> Organization: SYSGO AG X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 14:22:44 -0000 On Wed, 12 Jun 2013 13:58:00 -0700, David Wolfskill wrote: > On Tue, Jun 11, 2013 at 11:59:20PM -0500, Matthew D. Fuller wrote: > > ... > > Well, xfig isn't using anything particularly new or exciting in X; I > > doubt it's even hitting any OpenGL paths or the like. I'd start by > > just slapping a gdb on it and see if I can get a hint of where in what > > library it's stuck; maybe that'll make the answer obvious... > > I tried that, found that it was last in DoLayout(), part of > x11-toolkits/Xaw3d. So I rebuilt x11-toolkits/Xaw3d with debugging, as > well; found that Xaw3d was being invoked from x11-toolkits/libXt; ebuilt > that with debugging. > > [...] > > Program received signal SIGTERM, Terminated. > 0x28206db1 in DoLayout (bbw=0x289eb600, width=0, height=0, > reply_width=0xbfbfc29e, reply_height=0xbfbfc29c, position=0 '\0') > at Box.c:179 > 179 for (i = 0; i < bbw->composite.num_children; i++) { > (gdb) bt > #0 0x28206db1 in DoLayout (bbw=0x289eb600, width=0, height=0, > reply_width=0xbfbfc29e, reply_height=0xbfbfc29c, position=0 '\0') > at Box.c:179 > #1 0x28207346 in PreferredSize (widget=0x289eb600, constraint=0xbfbfc3b4, > preferred=0xbfbfc39c) at Box.c:358 > #2 0x28283f86 in XtQueryGeometry (widget=0x289eb600, intended=0xbfbfc3b4, > reply=0xbfbfc39c) at Geometry.c:789 > #3 0x2822b71f in ComputeLayout (widget=0x289eb300, query=1 '\001', > destroy_scrollbars=1 '\001') at Viewport.c:589 > #4 0x28298454 in XtSetValues (w=0x289eb300, args=0x81b2120, num_args=0) > at SetValues.c:407 > #5 0x080e2589 in sel_mode_but (widget=0x289f1400, closure=0x8171944, > event=0xbfbfd404, continue_to_dispatch=0xbfbfce0b "\001\224'+(\004") > at w_modepanel.c:639 > #6 0x2828152f in XtDispatchEventToWidget (widget=0x289f1400, event=0xbfbfd404) > at Event.c:882 > #7 0x28281b03 in _XtDefaultDispatcher (event=0xbfbfd404) at Event.c:1367 > #8 0x28280b10 in XtDispatchEvent (event=0xbfbfd404) at Event.c:1423 > #9 0x08085768 in main (argc=Error accessing memory address 0x1e: Bad address. > ) at main.c:1551 The last few frames look just like what somebody reported back in 2005(!): http://lists.freebsd.org/pipermail/freebsd-x11/2005-September/002206.html In NetBSD's GNATS there is a PR for this issue and it includes a proposed fix, perhaps this solves the problems: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=32445 HTH, -- Thomas Mueller