Bug#510589: still crashing in 17.0-1

2013-03-04 Thread Daniel Kahn Gillmor
On Mon 2013-02-25 17:03:02 -0500, Daniel Kahn Gillmor wrote: I just got another crash with icedove 17.0.2-1, but i've been running nspr 2:4.9.5-1 (which i hadn't managed to rebuild with DEB_BUILD_OPTIONS=debug yet), so i don't have any specific assert() output to share yet. I'm re-building

Bug#510589: still crashing in 17.0-1

2013-02-25 Thread Daniel Kahn Gillmor
Control: found 510589 17.0.2-1 On Sat 2013-01-19 11:16:14 -0800, Daniel Kahn Gillmor wrote: I've rebuilt nspr 2:4.9.4-2 with this option and installed it; i'm also running icedove under gdb. I'll report if i get anything to replicate. I just got another crash with icedove 17.0.2-1, but i've

Bug#510589: still crashing in 17.0-1

2013-02-25 Thread Mike Hommey
On Mon, Feb 25, 2013 at 02:03:02PM -0800, Daniel Kahn Gillmor wrote: Control: found 510589 17.0.2-1 On Sat 2013-01-19 11:16:14 -0800, Daniel Kahn Gillmor wrote: I've rebuilt nspr 2:4.9.4-2 with this option and installed it; i'm also running icedove under gdb. I'll report if i get

Bug#510589: Fwd: Re: Bug#510589: still crashing in 17.0-1

2013-01-19 Thread Carsten Schoenert
Hello Mike, can you please take a look into this bug? You know more of the internal mystique of Icedove. :) This forwarded mail is the beginning of the interesting part that Daniel has posted. Thx Carsten Original-Nachricht Betreff: Re: Bug#510589: still crashing in 17.0-1

Bug#510589: still crashing in 17.0-1

2013-01-19 Thread Mike Hommey
On Fri, Jan 18, 2013 at 04:31:19PM -0500, Daniel Kahn Gillmor wrote: On Wed 2013-01-16 12:10:22 -0500, Daniel Kahn Gillmor wrote: woo, yay(?), i got one! and i just got another one: [New Thread 0x7fff8fdfd700 (LWP 10439)] Program received signal SIGSEGV, Segmentation fault.

Bug#510589: still crashing in 17.0-1

2013-01-19 Thread Daniel Kahn Gillmor
On 01/19/2013 03:57 AM, Mike Hommey wrote: You may want to rebuild nspr with DEB_BUILD_OPTIONS=debug, seeing your backtrace, you'll likely hit some assert, which may give better insight. I've rebuilt nspr 2:4.9.4-2 with this option and installed it; i'm also running icedove under gdb. I'll

Bug#510589: still crashing in 17.0-1

2013-01-18 Thread Daniel Kahn Gillmor
On Wed 2013-01-16 12:10:22 -0500, Daniel Kahn Gillmor wrote: woo, yay(?), i got one! and i just got another one: [New Thread 0x7fff8fdfd700 (LWP 10439)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffcf1ff700 (LWP 28932)] pt_PostNotifyToCvar (cvar=0x0,

Bug#510589: still crashing in 17.0-1

2013-01-16 Thread Daniel Kahn Gillmor
On Mon 2013-01-14 13:00:06 -0500, Daniel Kahn Gillmor wrote: i've installed a bunch of other -dbg packages (e.g. libc6-dbg, libnspr4-dbg, libnss3-dbg, ...), in the hopes that that will give me more feedback in the next crash. woo, yay(?), i got one! Program received signal SIGSEGV,

Bug#510589: still crashing in 17.0-1

2013-01-16 Thread Carsten Schoenert
Hello Daniel, Am 16.01.2013 18:10, schrieb Daniel Kahn Gillmor: On Mon 2013-01-14 13:00:06 -0500, Daniel Kahn Gillmor wrote: i've installed a bunch of other -dbg packages (e.g. libc6-dbg, libnspr4-dbg, libnss3-dbg, ...), in the hopes that that will give me more feedback in the next crash.

Bug#510589: still crashing in 17.0-1

2013-01-16 Thread Sebastian Ramacher
On 2013-01-16 12:10:22, Daniel Kahn Gillmor wrote: On Mon 2013-01-14 13:00:06 -0500, Daniel Kahn Gillmor wrote: i've installed a bunch of other -dbg packages (e.g. libc6-dbg, libnspr4-dbg, libnss3-dbg, ...), in the hopes that that will give me more feedback in the next crash. woo,

Bug#510589: still crashing in 17.0-1

2013-01-16 Thread Daniel Kahn Gillmor
On 01/16/2013 12:29 PM, Sebastian Ramacher wrote: Looks like #672860. I had the same traceback when using icedove and enigmail to view signed mails. it certainly does look similar to me. --dkg signature.asc Description: OpenPGP digital signature

Bug#510589: still crashing in 17.0-1

2013-01-16 Thread Daniel Kahn Gillmor
On 01/16/2013 12:25 PM, Carsten Schoenert wrote: Hmm, o.k. Can you provide a longer entry from the end? The few lines are to short to see anything. i'm afraid that was the full backtrace. do you want more lines from icedove-dbg.log? how is that file organized? the part of the line before

Bug#510589: still crashing in 17.0-1

2013-01-14 Thread Carsten Schoenert
Hello Am 13.01.2013 18:32, schrieb Daniel Kahn Gillmor: thanks for the suggestion! i've tried this, but all the stack frames are still anonymous memory locations (weirdly, with the exception of a single non-helpful line in thread 35: That's what I mean with other packages with debugging

Bug#510589: still crashing in 17.0-1

2013-01-14 Thread Daniel Kahn Gillmor
On 01/14/2013 11:45 AM, Carsten Schoenert wrote: As I can see you use a core dump, mhh as I remember right (I'm not at home while writing this mail) the gdb always show the package there the symbol would come from while the binary is running inside. So please try to icedove inside the gdb.

Bug#510589: still crashing in 17.0-1

2013-01-13 Thread Daniel Kahn Gillmor
On 01/13/2013 04:08 AM, Carsten Schoenert wrote: You have to call backtrace with a few more arguments, icedove is a multi threaded program, so we must to see all the threads. So please try (gdb) thread apply all bt thanks for the suggestion! i've tried this, but all the stack frames are still