On Wed, Jan 13, 2010 at 09:07:18AM +0100, Daniel Leidert wrote: > It would still be nice to see, at which point in the gcu source code the > call appears. Can you install libgcu-dbg and libglib/libgtk*-dbg and > send the backtrace please?
I did that before obtaining the backtrace. ii libgcu-dbg 0.8.7-2+b1 GNOME chemistry utils (debugging symbols) ii libglib2.0-0-dbg 2.16.6-2 The GLib libraries and debugging symbols ii libgtk2.0-0-dbg 2.12.12-1~lenn The GTK+ libraries and debugging symbols ii libgtkglext1-dbg 1.2.0-1 OpenGL Extension to GTK+ (debugging symbols) It's interesting that even with libgobject's debug library in place (provided by libglib2.0-0-dbg), some of its functions still aren't resolved. That terminal 0x00000000 on the backtrace makes me wonder if there's an uncaught null pointer involved. - Nicholas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org