Bug#825852: icedove: segfault

2016-05-31 Thread George B.
On 30/05/16 22:33, Carsten Schoenert wrote: Can you please describe what you have done and on which action the segfault is happening? I'm afraid I don't have anything specific - I was just clicking around looking at emails as usual I think and it crashed. Best regards, George

Bug#825852: icedove: segfault

2016-05-30 Thread Carsten Schoenert
On Mon, May 30, 2016 at 10:22:30PM +0100, George B. wrote: > Thanks for the hint! I attach the output of `thread apply all bt` (as a file > because it is so big). Can you please describe what you have done and on which action the segfault is happening? So I can only see something related to

Bug#825852: icedove: segfault

2016-05-30 Thread George B.
On 30/05/16 21:49, Carsten Schoenert wrote: I can't see any segfault here, did you mentioned the hints on https://wiki.debian.org/Icedove#Debugging Please create a log decribed on the wiki page. otherwise it's impossible to grab the needed informations. Hi Carsten, Thanks for the hint! I

Bug#825852: icedove: segfault

2016-05-30 Thread Carsten Schoenert
Hello George, On Mon, May 30, 2016 at 08:07:33PM +0100, George B. wrote: > Package: icedove > Version: 1:45.1.0-1 > Severity: normal > > Hello, > > I had icedove crash with the follwing backtrace: > > ``` I can't see any segfault here, did you mentioned the hints on

Bug#825852: icedove: segfault

2016-05-30 Thread George B.
Package: icedove Version: 1:45.1.0-1 Severity: normal Hello, I had icedove crash with the follwing backtrace: ``` #0 0x7fc4b4ec2c09 in raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/pt-raise.c:36 resultvar = 0 pid = #1 0x7fc4b0d8e7e1 in