Timo Sirainen wrote:
I tried to get a coredump with the infromation an the provided web-page. However i never got a dump.
You can't get core dumps easily from login processes. Oh d'oh, that is true. I always do the gdb trace trick. Maybe we should document this.
The easiest way to get a backtrace is:
- Set login_processes_count = 1
- Restart Dovecot and make sure you have only a single managesieve-login process.
- gdb -p
pidof managesieve-login- Give "c" command to gdb.
- Log in, causing the crash
- gdb should have now stopped, give it "bt full" command. You can also use netstat -plan to see which of the managesieve processes you are connected to (then there is no need to change your config). There should be one ESTABLISHED connection to a managesieve-login originating from your host. The number listed before process name (i.e. managesieve-login) is the pid needed for gdb.
I used the packages provided by "deb http://xi.rename-it.nl/debian/ testing-auto main". I don't know if these contain the debugging symbols. So it seems i can't provide any further information.
Even without debugging symbols you should be able to get some kind of a backtrace. If you build the package from source, you can easily force it to compile with debug symbols. Open the debian/rules file and deactivate (remove or comment) the line 'dh_strip -a' in the build-arch make rule (line 130). (There is probably a nicer way using environment variables, but I never cared to find out how).
Regards,
-- Stephan Bosch stephan@rename-it.nl