On 11/11/2009 02:22:52 PM, Peter Bloomfield wrote:
> BTW: if you do go the terminal route, and you may be running in gdb
> for
> quite a while, it's worth handling broken pipes, as (for me) they
> also
>
> occur once or twice a day, and they stop gdb unless you handle them;
> at
> the gdb pr
On Nov 11, 2009, at 2:47 PM, Karl O. Pinc wrote:
[ snip ]
Allright. I just missed another crash.
I've done
ulimit -c unlimited
before running balsa. This should get me a core
file I can run gdb on to do a backtrace. Right?
Is this sufficient or should I muck about so I
can run balsa interac
On 11/07/2009 05:05:49 AM, Peter Bloomfield wrote:
>
> 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 "CRITICA
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
Package: balsa
Version: 2.3.25-1
Severity: normal
Hi,
Balsa has been crashing a lot on me lately. It appears
to happen when new mail arrives at the same time I do
something that opens a window, like replying to an email
or, perhaps, composing a new email.
This started when I upgraded to Lenny.
5 matches
Mail list logo
