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 2014-08-13 09: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/cyggobject-2.0-0.dll-gdb.py",
line 9, in <module>
     from gobject import register
   File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
     import gdb.backtrace
ImportError: No module named backtrace

This is actually an upstream issue due to an API change in gdb-7.7:

https://bugzilla.gnome.org/show_bug.cgi?id=623552

I'm building a glib2.0 update now that includes the latest upstream changes for the gdb scripts, which should fix this error message.

Thanks for reporting,

Yaakov


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


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