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 anonymous memory
locations (weirdly, with the exception of a single non-helpful line in
thread 35:
Thread 35 (LWP 17416):
#0 0x00007f37da62f64b in ?? ()
#1 0x0000076f00000000 in ?? ()
#2 0x00007f37bc82c188 in ?? ()
#3 0x00007f37bc8630e8 in ?? ()
#4 0x00000000000007d9 in ?? ()
#5 0x00007f378b9fecd0 in ?? ()
#6 0x00007fff347ffa1b in gettimeofday ()
#7 0x00000000000007da in ?? ()
#8 0x00000000000007d9 in ?? ()
#9 0x00000000000007d9 in ?? ()
#10 0x00007f37bc8630e8 in ?? ()
#11 0x0000076f00000002 in ?? ()
#12 0x0000000000000000 in ?? ()
)
> This looks like there are no debugging symbols. Without the symbols it's
> impossible to track down the error.
I have the corresponding icedove-dbg package -- what other package do i
need?
> just need the output of icedove made with the gdb while crashing. In
> the Icdove wiki page [1] are all the needed part to collect this data.
> Please check if the segfaults also happen while using a clean fresh
> profile without any extensions! Many problems happen to users that uses
> migrated User Profiles from Thunderbird 1.5. or 2.0.
the segfaults i've seen have not be trivially reproducible or tied to
any particular action. they happen after at least a day of active use
(and i process a lot of e-mail). This is not something i can actually
do with a fresh profile, or without the extensions i rely on (enigmail
in particular).
> If you can also collect data from the icedove activity itself [2] so
> please do.
this seems to want me to run icedove while creating a huge activity log.
I'll try this, but given the amount of activity between crashes, i
suspect this file is likely to be enormous. I'll see what i can do with
it, though.
> Depending on point the segfault happen it's maybe necessary to install
> more packages with debugging symbols.
which packages should i install beyond icedove-dbg?
>> fwiw, I'm running icedove from experimental:
>
> Strange, all my various icedove versions doesn't segfaulting for a long
> time. Which debian release do you use?
I use primarily wheezy, but with some packages from sid and experimental.
--dkg
signature.asc
Description: OpenPGP digital signature
