Hi Daniel,
On Sun, Nov 10, 2013 at 10:56:18PM -0500, Daniel Kahn Gillmor wrote:
> On 11/09/2013 07:44 AM, Guido Günther wrote:
> > That's
> >
> > while ((c = *fmt++) != 0) {
>
> thanks for the diagnosis.
>
> > So we at least know that the format string used is bad and that it tries
> > to print a size. Since this is fairly generic code I'd suspect that
> > something gets corrupted beforehand and this is just a fallout. It'd be
> > great to see if this is reproducable. Also running under valgrind might
> > give some insight but it crashes are rare that's probably to much to ask
> > for.
>
> I can't imagine actually running icedove under valgrind for my daily
> usage, sorry. Too resource-intensive for my mail volume. And while I
> have had multiple crashes with 24.0, (probably once every 2-3 days), i
> can't have my mail all backlogged by running it under valgrind,
> especially not on a process as huge as icedove.
Yeah, absolutely. I'd be great to know if the backtraces look identical
within gdb then or if they happen at different places.
> Reducing the bloat in icedove would certainly make it easier to get
> diagnostics :/
Very true.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
