On May 26, 2009, at 5:46 AM, Rui Carneiro wrote:
Citando Timo Sirainen <t...@iki.fi>:
So valgrind didn't find anything wrong.
We should ignore LEAK SUMMARY?
At least for now. Memory leaks don't cause crashes.
What does gdb show as the backtrace?
My gdb is not writing where he should (or not writing at all). This
shouldn't be enough?
mail_executable = /usr/local/libexec/dovecot/gdbhelper /usr/local/
libexec/dovecot/imap
It's not writing /tmp/gdbhelper* files when crashing? Anyway there's
also one guaranteed way to get backtrace. Remove the gdbhelper and
then run:
gdb -p `pidof imap`
cont
<make it crash>
bt full
