This is the mail archive of the
cygwin
mailing list for the Cygwin project.
glib errors with latest gdb
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin <cygwin at cygwin dot com>
- Date: Wed, 13 Aug 2014 10:28:23 -0400
- Subject: glib errors with latest gdb
- Authentication-results: sourceware.org; auth=none
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
Reverting to the previous gdb solves the problem.
My actual use case involves emacs-w32 rather than gvim, but I tested
gvim also to make sure that this wasn't emacs-specific. The error is
more than cosmetic, at least in the emacs case; gdb freezes and has to
be killed from the Task Manager.
Ken
--
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