Re: [Evolution] Logwatch reports segmentation faults in Evolution

[Patrick O'Callaghan <poc usb ve>]

On Fri, 2022-10-07 at 15:11 -0500, Tim McConnell via evolution-list
wrote:
> On Mon, 2022-09-26 at 07:15 +0200, Milan Crha via evolution-list
> wrote:
> > On Fri, 2022-09-23 at 12:47 -0500, Tim McConnell via evolution-list
> > wrote:
> > > I'm on Evolution 3.45.3-2 and my logwatch has been reporting
> > > segmentation faults for the last few days.
> >
> >         Hi,
> > I do not know what logwatch is, nor how one gets more detailed
> > information out of it, but if you face evolution process crashes,
> > then
> > I suggest to run it from a terminal under gdb and get the backtrace
> > when the crash happens. Note the gdb will catch it and will wait
> > for
> > an
> > input while the GUI will look frozen. A command can be:
> >
> >    $ gdb evolution --ex r
> >
> > and once it stops do:
> >
> >    (gdb) bt
> >
> > to print the current thread backtrace. An information before this
> > command can be useful too, possibly showing some runtime warnings.
> > To
> > quit gdb simply execute command in its prompt:
> >
> >    (gdb) q
> >
> > Please check the backtrace for any private information, like
> > passwords,
> > email addresses, server addresses,... I usually search for "pass"
> > at
> > least (quotes for clarity only).
> >
> >         Bye,
> >         Milan
> >
> > _______________________________________________
> > evolution-list mailing list
> > evolution-list gnome org
> > To change your list options or unsubscribe, visit ...
> > https://mail.gnome.org/mailman/listinfo/evolution-list
>
> Hi Milan, 
> Does running gdb evolution --ex r create any files or take up disk
> space? The reason I ask is it (Evolution) still crashes, but there
> aren't any repeatable steps. It crashes at random so maybe if I have
> it
> running in GDB maybe I could get a back trace. But it could be days
> before it crashes, so I'm trying to figure out how to be able to get
> a
> back trace of the issue and not fill up my hard drive. I'm on Version
> 3.46.0-2 in Debian Testing(Bookworm) btw. 

"gdb something --ex r" will just start "something" under the debugger
and then let it run until it either exists or crashes. It won't create
any files on its own.

poc