|
2014-05-22 17:51, Phillip Susi skrev:
The gtkmm tutorial contains a section that describes how to use the gdb debugger to see where an exception is thrown in a signal handler.-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to track down a bug that prints this: (gpartedbin:15278): glibmm-CRITICAL **: unhandled exception (type Glib::Error) in signal handler: domain: g_convert_error code : 1 what : Invalid byte sequence in conversion input I'm trying to understand this glibmm exception stuff and so far it sounds to me like there is a C++ wrapper around a glib string conversion function *somewhere* that gets back a Glib::Error return, and throws that as a C++ exception, which is uncaught, and the default handler catches it and queues a callback that is later run from the main loop and prints this message. The problem is that by the time the message is printed, the original cause has been removed from the stack. Looking at the glibmm sources, I can't even figure out what function is responsible for queuing the call to Glib::exception_handlers_invoke(). So how can I find the source of this error? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTfhzpAAoJEI5FoCIzSKrwv7wH/0kZ7Xj2q/KyHVgqmK/xFCUo TwfHu2Jp9fxBKhR+V0TQqJiaxgHIH/gqoeBQK//lGepeoOAzs6ZAO48tzeyT8PYg HnxyZ6IkmrppTzbILQPbTFkTd7DuTcRsfnnWbcivwZcunLaq7nBUYZ6Q1D+njg9L qaHo6rqGq1/24tdvki7NWLNdedGfT+fsazQcYIpf0gG7Sm1t9H62XtyCXED0VeQJ QVAKj9VYY5exZryJnxP2zzPKDCJflPjA9I76CBJVO5Z2OATikyQJZLb6PG0A11LF q/KRK9CGaFpy6YVwplSm8TUgwKP9O2fUpz4kHJnn9aATcjDV1infRSLV5AJj+pQ= =BjHk -----END PGP SIGNATURE----- _______________________________________________ https://developer.gnome.org/gtkmm-tutorial/stable/sec-exceptions-in-signal-handlers.html.en |