Re: [Evolution] Evolution doesn't start

[Milan Crha <mcrha redhat com>]

On Mon, 2015-02-23 at 11:34 +0100, Jörg Jenetzky wrote:
> Hi Andre,
>
> my previous try to get the log file through from 22.02.2015 18:13 
> was rejected because of exceeding data:
>
> Am 23.02.2015 um 10:27 schrieb evolution-list-owner gnome org:
>
> > Your request to the evolution-list mailing list
> >
> >     Posting of your message titled "Re: [Evolution] Evolution 
> > doesn't
> > start"
> >
> > has been rejected by the list moderator.  The moderator gave the 
> > following reason for rejecting your request:
> >
> > "Your message was had 5.6MB; please trim it to less than 40 KB in 
> > size."
>
> Am 22.02.2015 um 16:42 schrieb Andre Klapper:
> > [...]
> >
> > Let me quote my previous email again:
> >
> > Please make sure that Evolution/glib/gtk3 debug packages are 
> > installed
> just checked: There is only <glib-2.0> to be found on the system, 
> though I installed any available dbg-stuff from the repositories.
>
> I meanwhile have Valgrind installed, as suggested on
> https://wiki.ubuntu.com/DebuggingProgramCrash.
> I ran it with
> > G_SLICE=always-malloc G_DEBUG=gc-friendly  valgrind -v --
> > tool=memcheck --leak-check=full --num-callers=40 --log-
> > file=valgrind.log evolution
> Reply was "killed".
>
> The log-file is *not* attached - it had 4,9 MB.

        Hi,
do you know that you were asked to provide a backtrace of the crash? 
There was absolutely no mentioning of the valgrind at all. Your 
previous gdb output only missed an invocation and output of a
"thread apply all bt" gdb command. That will show where evolution 
crashed, and eventually why.

Of course, you can start to play with underlying files and try to 
guess which one is causing the crash, but that might be quite time 
consuming, and you may eventually skip some data which are not broken 
at all. The backtrace is there to help you find out the right place 
quickly and accurately.
        Bye,
        Milan