Justin Pryzby wrote:
Perhaps you could run the process under valgrind, and get a backtrace
sometime before the crash? Sometimes this points to the source of the
problem, rather than the thing that ultimately causes the SEGV.
I ran "valgrind evolution 2> debug.txt. Attached is the debug stuf
Perhaps you could run the process under valgrind, and get a backtrace
sometime before the crash? Sometimes this points to the source of the
problem, rather than the thing that ultimately causes the SEGV.
Thanks.
--
Clear skies,
Justin
References
[0] http://bugs.debian.org/cgi-bin/bugreport.cg
2 matches
Mail list logo
