Re: repeatable balsa crash



On 09/09/2008 09:34:46 AM, Mario Mikocevic wrote:
Hi,

On 09/08/2008 05:27:44 PM, Peter Bloomfield wrote:
[ crash details snipped ]

I haven't reproduced that yet (still trying!). Could you run Balsa in gdb with --g-fatal-warnings, and trigger one of these? A backtrace for one of those failed assertions might be more helpful than the eventual segv.

Didn't get much far from starting balsa :]

% gdb
GNU gdb Fedora (6.8-17.fc9)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu".
(gdb) file /usr/bin/balsa
Reading symbols from /usr/bin/balsa...Reading symbols from /usr/lib/debug/usr/bin/balsa.debug...done.
done.
(gdb) run --g-fatal-warnings
Starting program: /usr/bin/balsa --g-fatal-warnings
[Thread debugging using libthread_db enabled]
[New Thread 0xb7ef0760 (LWP 12586)]

** WARNING **: no name for stock_id "balsa_trash_empty"
aborting...

That's another problem. Could remove temporarilty "empty trash" button from your toolbar? We will have to track the button icon problem down but let's first debug the mailbox crash...

Pawel


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]