Re: Logwatch reports segmentation faults in Evolution

On Sun, 2022-10-09 at 22:36 +0100, Patrick O'Callaghan wrote:
> On Sun, 2022-10-09 at 14:27 -0500, Tim McConnell via evolution-list
> wrote:
> > > I would think so. The debugger just sets a signal trap, so I
> > > wouldn't
> > > expect the CPU usage to change, as Evo will run at normal speed
> > > until
> > > something "interesting" happens.
> > 
> 
> > [...]
> 
> > That's good, it took a week for the segfault to reappear and once
> > again
> > , I have no way of knowing why. it did it after I had the computer
> > running overnight. The only "consistent" thing is I'm prompted to
> > sign
> > into Google Contacts before the crash. Even that makes little sense
> > due
> > to me having don't ask on this device checked.
> 
> Did you get a stack trace when it happened?
> 
> > Maybe because I have 2
> > gmail accounts it's checking(?)but I doubt that, I'm reasonably
> > sure
> > Evolution can get multiple IMAP accounts with no problems. 
> 
> It definitely can.
> 
> poc
> _______________________________________________
> evolution-list mailing list
> [email protected]
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list


>Did you get a stack trace when it happened?
Don't I wish :( I didn't have gdb running yet. Next time though, I have
evolution in gdb now. 
-- 
Tim McConnell <[email protected]>
_______________________________________________
evolution-list mailing list
[email protected]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list