This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glib errors with latest gdb

On Aug 13 16:57, Corinna Vinschen wrote:
> On Aug 13 10:28, Ken Brown wrote:
> > I'm getting errors with the latest gdb when trying to debug programs that
> > depend on glib.  Here's an example, run from an xterm window:
> > 
> > $ gdb /usr/bin/gvim
> > GNU gdb (GDB) 7.8
> > [...]
> > Reading symbols from /usr/bin/gvim...(no debugging symbols found)...done.
> > (gdb) r
> > Starting program: /usr/bin/gvim
> > [New Thread 4860.0x1b44]
> > Traceback (most recent call last):
> >   File "/usr/share/gdb/auto-load/usr/bin/", line
> > 9, in <module>
> >     from gobject import register
> >   File "/usr/share/glib-2.0/gdb/", line 3, in <module>
> >     import gdb.backtrace
> > ImportError: No module named backtrace
> I see this error, too.  Unfortunately I'm not a python guru so this
> is rather opaque to me.  gdb itself doesn't provide a gdb.backtrace
> method, afaics.
> However, despite this message, gvim starts normally.  And emacs-nox as
> well as many other CLI applications can be started just fine, too.
> But GDB hangs with emacs-X11 for some reason, even if I disable the
> python modules.  From a quick GDB session it's not clear why this occurs :(

I reported the problem upstream in a bugzilla entry already handling
strange GDB hangs:


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgpjY70o_fKT1.pgp
Description: PGP signature

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]