Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=701604
--- Comment #41 from Milan Crha <mcrha(a)redhat.com> 2011-12-22 03:16:54 EST ---
OK, I would move this to Fedora 16, but before that, are you sure this is the
same issue as this bug report? I would like to see updated backtrace from
Fedora 16, with debug information at least from evolution-data-server,
evolution and gtkhtml3, and if you can reproduce this reliably, then even the
valgrind log may help here, because this seems like a memory corruption issue.
Thanks in advance.
To get backtrace, just run evolution under gdb like this:
$ gdb evolution --ex r --ex "t a a bt" --ex q
and reproduce the issue. At the end the gdb will ask you whether you want to
quit. Answer "y". Then get its output. Make sure it'll not include any
private
information, like email addresses, passwords or server addresses you do not
want to share in public.
To get valgrind log run evolution like this:
$ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
and try to reproduce the issue. Note that evolution will be significantly
slower due to all memory checking. Also note that valgrind can avoid certain
crashes, which it only logs into the file, thus even if evolution will not
crash then the log.txt file can contain information about the issue.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.