On 2009-07-25 "David A. Greene" <d...@cray.com> wrote: > On Saturday 25 July 2009 02:16:50 you wrote: >>> exim4[7068]: segfault at 2c ip 782ebf3 sp bfb32aac error 4 in >>> libc-2.9.so[b77b8000+13c000]
>> [...] >> Could you provide a backtrace > How do I generate one? You would run exim inside GNU debugger, i.e.: 1. install exim4-daemon-heavy-dbg 2. gdb /usr/sbin/exim4 run -bd [ start behavior that causes crashes] bt >> * debugging output > From where / how do I generate it? Run exim with debugging arguments, then trigger the crash, ie.: exim4 -bd -d+all If this is a production system it might be possible to run these tests in a testing instance, using a different spooldirectory against the broken db files. thanks, cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
