Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Jun 2013 23:59:20 -0500
From:      "Matthew D. Fuller" <fullermd@over-yonder.net>
To:        David Wolfskill <david@catwhisker.org>
Cc:        x11@freebsd.org
Subject:   Re: Help debugging xfig lockup?
Message-ID:  <20130612045919.GA1940@over-yonder.net>
In-Reply-To: <20130612031624.GS1369@albert.catwhisker.org>
References:  <20130612031624.GS1369@albert.catwhisker.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 11, 2013 at 08:16:24PM -0700 I heard the voice of
David Wolfskill, and lo! it spake thus:
> 
> A few days ago, I happened to want to use it .... and I find that it
> starts OK, but once a Drawing mode or an Editing action is selected,
> it locks up -- no other selection appears to have an effect, and
> causing the application to exit requires some "external assistance"
> (e.g., from another xterm, "pkill xfig").

As a data point (I also use xfig somewhat rarely but repeatedly over a
decade+), I just fiddled with it a bit here without trouble, with
ports up to date as of yesterday, and -CURRENT as of the weekend.

I'd guess the difference is probably in details of X.  I'm using the
radeon driver on non-WITH_NEW_XORG.


> But debugging an X11 application is something that leaves me rather
> wondering how to go about it.  Any clues?

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...

Going into draw/edit mode does involve changing the cursor; maybe
that's the significant bit?


-- 
Matthew Fuller     (MF4839)   |  fullermd@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130612045919.GA1940>