GNU bug report logs - #17411
24.4.50; emacs_backtrace.txt

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Mon, 5 May 2014 20:09:02 UTC

Severity: normal

Tags: moreinfo

Merged with 17340, 17347, 17436

Found in version 24.4.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: lekktu <at> gmail.com, 17411 <at> debbugs.gnu.org
Subject: bug#17411: 24.4.50; emacs_backtrace.txt
Date: Tue, 13 May 2014 17:19:50 -0400

>> The "eassert (length (i) > 0)" does catch this case already.  We could
>> add another assert which is looser (i.e. one that would not be caught by
>> a "somewhat sane interval with a non-positive length"), but I'm not sure
>> how to formally define "hopelessly messed up".
> You could display the values on your system in a debugger, and after
> some time you should have a good idea what isn't messed up.

The problem is that it's not worth the trouble: knowing if the values are
sane or not isn't that interesting, so we'd really want to *see*
the values.  I'd "fprintf (stderr, ...)", but that wouldn't work under
w32 would it?


        Stefan
This bug report was last modified 9 years and 143 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.