Re: Segmentation faults in DBMail 3.2

Okay sorry for the spam, i am not used to gdb. :(
Now complete:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffef9c4700 (LWP 12352)]
0x0000000000418cd5 in _ic_status_enter (D=0x735b80) at imapcommands.c:1520
1520                self->mailbox->condstore = true;
(gdb) bt
#0  0x0000000000418cd5 in _ic_status_enter (D=0x735b80) at 
imapcommands.c:1520
#1  0x00000000004611df in dm_thread_dispatch (data=0x735b80, user_data=0x0)
     at server.c:226
#2  0x00007ffff768188c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff7680f05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ffff5ffa182 in start_thread (arg=0x7fffef9c4700)
     at pthread_create.c:312
#5  0x00007ffff5d26efd in clone ()
     at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111



Am 05.01.15 um 13:04 schrieb [email protected]:
> Okay sorry, that wasn't the segfault, i finally got it:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffef9c4700 (LWP 12352)]
> 0x0000000000418cd5 in _ic_status_enter (D=0x735b80) at imapcommands.c:1520
> 1520                self->mailbox->condstore = true;
>
>
>
> Am 05.01.15 um 13:00 schrieb Reindl Harald:
>>
>>
>> Am 05.01.2015 um 12:57 schrieb Claas Kähler:
>>> 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!
>>
>> not that much without the informations *before* to get a context i guess
>>
>>> 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.
>>
>>
>>
>> _______________________________________________
>> DBmail mailing list
>> [email protected]
>> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
>
>
>
> _______________________________________________
> DBmail mailing list
> [email protected]
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail