[Users] [Bug 4385] Fedora reporting kernel crashes related to Claws Mail

[Dustin Miller]

On Thu, 24 Sep 2020 08:41:12 +0000
noreply at thewildbeast.co.uk wrote:

> https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4385
> 
> --- Comment #27 from Jeremy Nicoll <jn.wb.bzc.0306 at letterboxes.org>
> --- Comment on attachment 2102
>   -->
> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=2102
> Entire gdb output - personal information removed
> 
> Just for information - the file you uploaded it contains a tiny
> amount of info from gdb - just 4 lines at the top saying it is
> starting claws, and just 4 lines at the bottom saying it's got
> control again because claws crashed.
> 
DM: Thanks for this, Jeremy. I haven't ever used gdb so this is helpful
to know.

DM: Edward, Jeremy's comment here is a good corrective to my previous
posts on this. So I'm guessing Paul's earlier comment was probably
because you had copied part of the gdb-specific output rather than the
claws-specific output, but I'm not sure on that.

DM: Interesting that you found the similar issue from a year ago. Seems
like the first thing that needs to be figured out is whether the bug is
with Claws or with one of its supporting libraries. Not sure how to go
about doing that, but hopefully you and/or the developers will be able
to come up with a good workaround or solution for you. Cheers, ---Dustin
> 
> ALL the rest of the output is from claws, and is the "debug trace"
> that claws produces when run with the "--debug" flag (in this case
> because gdb was told to start claws by "run --debug").  These lines
> show what claws was doing and why it was doing it... with as much or
> as little info as the claws programmers thought they'd need when
> trying to follow the workings of claws.  Ideally it shows what claws
> was about to try to do just before the crash, but earlier on it will
> also show stuff from claws' setup which might help to explain what
> happened.   
> 
> gdb itself really only comes into play once claws has crashed, when
> gdb is then able to look at the contents of memory, create the stack
> trace etc, showing what the immediate aftermath of the crash looks
> like and hopefully just info, combined with the --debug info - for
> someone to work out why it happened.
> 
> -- 
> You are receiving this mail because:
> You are the assignee for the bug.