Hello Roland,
On Thu, Jan 15, 2015 at 04:04:23AM +0100, Roland Hieber wrote:
> I could reproduce it on a squeeze VM running icedove-3.0.11-1+squeeze15. The
> GDB
> output is attached below, and it looks similar. The backtrace even contains
> more
> information (see stack #3, the "line" contains an \n and is strangely off
> characters...)
It's strange and interessing that you see this issue backt to this old
version of Icedove, so possible it's a real old bug that happen not very
often.
But we from the Debian packaging side haven't enough man power to fix
such bugs explicitly in such old versions.
[...]
> I didn't find anything reated in the upstream tracker, besides that.
O.k. then I missed the real point and picked up a wrong upstream bug.
[...]
> OK, so what do I need to do to get a crash report for this kind of behaviour?
The right place for fixing such issues is the bugtracker at Mozilla, as
ist's a problem within the upstream source and not related to the Debian
packaging.
So I suggest to open up a new bug entry in the Mozilla bugtracker. But
the developers request mostly a reproducable way to catch the issue, so
please provide as much as possible the informations you can give. Append
your GDB sessions. But please expand before your GDB command to
'thread apply all bt'
Icedove is a multithreaded application so you want propably see all
informations from all threads.
Please see https://wiki.debian.org/Icedove#Starting_Debugging for more
informations.
If you open up the entry on Mozilla please give back the forwarding
adress and append this to this bug here. It's easiest to do with the
'bts' command. Also set a tag 'upstream'.
$ bts forwarded 768001 http:/bugzilla.mozilla.org/foo/...
$ bts tag 768001 upstream
Regards
Carsten
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
