Re: Segmentation faults in DBMail 3.2
Claas Kähler <[email protected]>
| Newsgroups | gmane.mail.imap.dbmail |
|---|---|
| Message-ID | <[email protected]> |
Hey Paul, i did what you told me. Gdb says: Program received signal SIGPIPE, Broken pipe. 0x00007ffff600135d in write () at ../sysdeps/unix/syscall-template.S:81 81 ../sysdeps/unix/syscall-template.S: File or directory not found. It happens if an apple mail client trys to connect. I hope this is helpfull! Am 28.12.14 um 12:43 schrieb Paul J Stevens: > > On 04-12-14 15:56, Claas Kähler wrote: >> Hallo, >> >> i got an annoying segmentation fault from time to time in dbmail-imapd. >> I am not able to restart the service directy and have to wait for a few >> minutes. Afterwards it will work agian. Has anybody else this problem >> too and found a solution? > I've had more reports of this. > >> In the attachment you will find a strace output and a coredump. > If you could reproduce this with gdb, instead of strace it would be very > helpful. > > Compile dbmail with debugging symbols: > > dbmail-3.2.2 $> CFLAGS=-g ./configure --enable-static=yes > dbmail-3.2.2 $> make > dbmail-3.2.2 $> sudo kill `pidof dbmail-imapd` > dbmail-3.2.2 $> gdb src/dbmail-imapd > gdb> run -D -f /path/to/your/dbmail.conf > > wait for crash... > *crash on segfault* > > gdb> bt > > cut and paste the output of bt. > > gdb> quit > dbmail-3.2.2 $> sudo /usr/sbin/dbmail-imapd > > > Of course stopping and restarting the installed version of dbmail-imapd > is only necessary if you are doing this on your production machine. > > > >