How to create a backtrace when gdb hangs X?
Adam Jackson
ajackson at redhat.com
Mon Apr 2 13:44:18 UTC 2007
On Sun, 2007-04-01 at 09:06 -0400, Matthias Clasen wrote:
> On Sun, 2007-04-01 at 14:37 +0200, dragoran wrote:
> > The last gaim update crashes for me when I change my status to away
> > without entering a message or when I change it to invisible.
> > I filled a bug here:
> > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234399
> > Its not possible to debug this because when it crashes inside gdb X hangs.
> > When I kill the gdb process (from a vt) X is back to normal... but still
> > no backtrace...
> > I tryed to get a backtrace from a core file ... but useless see the
> > bugreport.
> > Any ideas what I can do to debug this?
> >
>
> You can either run the hanging app in a nested X instance (Xnest or
> Xephyr), or turn on AllowDeactivateGrabs in your xorg.conf
Alternatively, ssh in from another machine and run the gdb process from
the ssh session.
- ajax
More information about the fedora-devel-list
mailing list