Hello Thomas, On Sat, Aug 06, 2016 at 08:27:11PM +0200, Thomas Florek wrote: > ... am not sure, if I did it right, but enclosed find the gdb logfile > > I will give more detailed info, if needed and I would be able ;)
the log looks good so far, but I can't see a segfault message. So the log is mostly useless for us, unfortunately. [SNIP > Type "apropos word" to search for commands related to "word"... > Reading symbols from /usr/lib/icedove/icedove-bin...Reading symbols from > /usr/lib/debug//usr/lib/icedove/icedove-bin...done. > done. > (gdb) handle SIGPIPE nostop > Signal Stop Print Pass to program Description > SIGPIPE No Yes Yes Broken pipe > (gdb) handle SIG38 nostop > Signal Stop Print Pass to program Description > SIG38 No Yes Yes Real-time event 38 > (gdb) run ... > Thread 1 "icedove-bin" received signal SIG38, Real-time event 38. Icedove created a SIG38 signal here, nothing relevant. From here down there are "just" messages about various threads Icedove was starting and closing. ... > Thread 1 "icedove-bin" received signal SIG38, Real-time event 38. > [Thread 0x7fffd9bff700 (LWP 5139) exited] > [New Thread 0x7fffd9bff700 (LWP 5165)] > [New Thread 0x7fffbb8ff700 (LWP 5168)] > [Thread 0x7fffbb8ff700 (LWP 5168) exited] > [Thread 0x7fffd9bff700 (LWP 5165) exited] > [New Thread 0x7fffbb8ff700 (LWP 5170)] > [New Thread 0x7fffd9bff700 (LWP 5171)] > [New Thread 0x7fffbaefb700 (LWP 5172)] > [New Thread 0x7fffba6fa700 (LWP 5173)] > [New Thread 0x7fffb9ef9700 (LWP 5174)] Why Icedove is here exiting normaly? Do you have closed the application here? > [Inferior 1 (process 5114) exited normally] > (gdb) exir t > Undefined command: "exit". Try "help". > (gdb) quit You closed gdb to early here so you don't see any information about the threads that was running. You need here to call 'thread apply all bt' to see this information. But only if Icedove was segfaulting, otherwise we (you) don't see anything that's useful to solve the problem. Regards Carsten
