On 11/06/2009 11:18:12 PM Fri, Karl O. Pinc wrote:
On 11/06/2009 05:57:51 PM, Peter Bloomfield wrote:
>
> That's probably not caused by two instances of Balsa--it's an
> internal
>
> check on the code.  If it's reproducible, could you run Balsa under
> gdb
> with --g-fatal-warnings and get a back-trace?  That would be really
> helpful.

What do you mean by "with --g-fatal-warnings"?  I assume this is a
compiler flag?  (It's not an argument to gdb or balsa....)

Sorry, I should have been clearer: "--g-fatal-warnings" is an argument for any Gtk-based app. You can use it like this:

o at the console, enter:

gdb path/to/balsa
r --g-fatal-warnings

o when Balsa issues the "CRITICAL" warning, it gets promoted to an error, and gdb stops; at that point, type

bt

and gdb will print the backtrace. It's good that you installed balsa-dbg--it makes the backtrace actually worth something!

Peter

Attachment: pgp6vxOTyf1Ie.pgp
Description: PGP signature

Reply via email to