Jorge, please update and try again.
next time this happens, don't just do a backtrace (bt), but als search for the first line that comes from dbmail code and do 'f <line>' I've been slowly working my way through Timo's imaptest testcases, fixing minor and not so minor problems with imap compliance. Jorge Bastos wrote: > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 0xb750bb00 (LWP 20095)] > > 0xb7db7167 in event_add () from /usr/lib/libevent-1.3e.so.1 > > (gdb) bt > > #0 0xb7db7167 in event_add () from /usr/lib/libevent-1.3e.so.1 > > #1 0x0804eb75 in imap_handle_exit (session=0x867f0e0, status=0) at > imap4.c:234 so in this case: f 1 this will give us a framedump and will show the codepath that leads to this particular case. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
