On Tue, Dec 9, 2014 at 12:06 AM, Dmitry Smirnov <only...@debian.org> wrote: > On Mon, 8 Dec 2014 22:51:28 Sandro Tosi wrote: >> no well maybe it is known but just mention it SIGSEGV without proving >> even a location memory or so it is hard to say if someone else already >> spotted it or now >> >> > Thanks, I'll run it in GDB and try to wait long enough for it to crash. > > Here is backtrace -- it didn't take long this time: > > ~~~~ > (gdb) thread apply all bt
I'm sorry, the way upstream wants backtraces is running these gdb commands: bt bt full thread apply all bt Can you please retake it with the output of all the 3 commands (I will have to write a guide to include into the package about taking tracebacks as upstream wants) Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
