Hello Micha, On Tue, Jun 14, 2016 at 04:58:12PM +0200, Micha Lenk wrote: > Well, I am not able to reproduce the issue reliably.
that's exact our problem, I run into Icedove crashs too, but they are really rare. Maybe 1 - 2 a month, and there are months thre nothing happen. > So, what I did is a > post-mortem analysis of the generated coredump. So I guess I can't > change the LANG env, right? Yes, only manually in the log file, and that's error prone. :-) > > Also if possible consider using "set substitute-path ..." inside the gdb > > session to a valide path. By this all can see the relvant source code > > there Icedove is crashing. > > > > https://sourceware.org/gdb/onlinedocs/gdb/Source-Path.html > > This is the icedove version installed in a stable release via APT, so I > have no clue what path to set here. I guess the Debian buildds know the > used paths. The used source code should be available in the Debian > archive, shouldn't it? Well, that's something for advanced gdb using, so no worry. The gdb trys to find the source like it was around while building. For the version 1:45.1.0~deb8u1 the buildd was using /build/icedove-tNL3mB/icedove-45.1.0/ Of course you dont have such a folder, so gdb cant find the source for the crashed function. You need to tell gdb a substion path (if you have downloaded and extracted the source for Icedove locally). For example, if have loaded the source from the package site https://packages.debian.org/source/stable/icedove on the bottom ... icedove_45.1.0.orig.tar.xz http://security.debian.org/debian-security/pool/updates/main/i/icedove/icedove_45.1.0.orig.tar.xz and extracted the archive into /home/user/icedove-source-45.1.0 than the substion comand would be: [start the debugger] set substitute-path /build/icedove-tNL3mB/icedove-45.1.0/ /home/user/icedove-source-45.1.0 run [the visible output] Regards Carsten
