On Fri, Oct 30, 2015 at 12:34:57AM -0400, Gabriel Filion wrote: > > please try to make a gdb log. Without further informations it's nearly > > impossible to catch the reason for the crash. > > > > https://wiki.debian.org/Icedove#Starting_Debugging > > youch ok. > > since I don't know what triggers the segfaults, I might need to run > icedove in gdb for hours or days :\
That's the (not so) funny part on catching such issues. > is there a way to make it dump a coredump when it crashes instead of > having to run it all the time in gdb? No, unfortunately not. There is no alternative for getting the needed informations. For finding wrong code we need not only the file and the respective line of code, we need some other variables as well like content of adress cells or functions. In the end it's nothing more than a little bit more than clicking a icon. On most of the other bugs there are segfaults reported we haven't enough information debugging informations for gettings things done. Regards Carsten
