Re: [Dovecot] Segmentation fault running doveadm import
I have followed the instructions about bug reports /generating cores located at http://dovecot.org/bugreport.html . You should consider adding additional info for cores & Red Hat Systems to your wiki, this link was very informative: http://www.akadia.com/services/ora_enable_core.html
As user "entrega":
-bash-3.2$ ulimit -c unlimited
In /etc/init.d/dovecot I have added "ulimit -c unlimited" at the beginning of the script
In /etc/dovecot/dovecot.conf I have added mail_debug=yes
*gdb --args doveadm import -u ox101@us.es mdbox:/backup/bacula-restores/buzones/mysite/15/b1/ox101/ "" all*
gdb --args doveadm import -u ox101@us.es mdbox:/backup/bacula-restores/buzones/mysite/15/b1/ox101/ "" all GNU gdb (GDB) Red Hat Enterprise Linux (7.0.1-32.el5_6.2) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/doveadm...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/doveadm import -u ox101@us.es mdbox:/backup/bacula-restores/buzones/mysite/15/b1/ox101/ '' all warning: no loadable sections found in added symbol-file system-supplied DSO at 0x2aaaaaaab000 [Thread debugging using libthread_db enabled] Executing new program: /usr/bin/doveconf [Thread debugging using libthread_db enabled] Executing new program: /usr/bin/doveadm [Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault. 0x00002aaaaaada400 in ?? () (gdb) bt full #0 0x00002aaaaaada400 in ?? () No symbol table info available. #1 0x0000000000409709 in ?? () No symbol table info available. #2 0x0000000000409b37 in doveadm_mail_try_run () No symbol table info available. #3 0x000000000040dddc in main () No symbol table info available.
No core generated, no relevant log info in /var/log/maillog. What can I do to make a better bug report?
Regards
Maria
----- Original Message ----- From: Timo Sirainen Sent: 02/22/11 09:35 AM To: Maria Arrea Subject: Re: [Dovecot] Segmentation fault running doveadm import
On Tue, 2011-02-22 at 06:58 +0000, Maria Arrea wrote: > Some more info: I am running dovecot 2.0.9 on Red Hat Enterprise Linux 5 > > Another question I would like to ask: I run the command doveadm > import as "entrega" user (see dovecot -n output in my previous mail ). > If I run the command as root also segfaults, and garbage is restored > (mails with binary data). If I run as "entrega" segfaults, but e-mails > are correctly restored Could you get gdb backtrace of the doveadm crash? For example: gdb --args doveadm import ...etc.. run bt full
On Tue, 2011-02-22 at 12:07 +0000, Maria Arrea wrote:
gdb --args doveadm import -u ox101@us.es mdbox:/backup/bacula-restores/buzones/mysite/15/b1/ox101/ "" all
Look good.
Reading symbols from /usr/bin/doveadm...(no debugging symbols found)...done.
But this doesn't. So:
Program received signal SIGSEGV, Segmentation fault. 0x00002aaaaaada400 in ?? () (gdb) bt full #0 0x00002aaaaaada400 in ?? () No symbol table info available. #1 0x0000000000409709 in ?? () No symbol table info available. #2 0x0000000000409b37 in doveadm_mail_try_run () No symbol table info available. #3 0x000000000040dddc in main () No symbol table info available.
Unfortunately the lack of debug symbols doesn't make this very useful.
No core generated, no relevant log info in /var/log/maillog. What can I do to make a better bug report?
Compile Dovecot without stripping out debug symbols (this is the default).
participants (2)
-
Maria Arrea
-
Timo Sirainen