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

Message #28 received at 17411 <at> debbugs.gnu.org (full text, mbox):

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: Re: bug#17411: 24.4.50; emacs_backtrace.txt
Date: Tue, 13 May 2014 15:32:13 -0400

>> > So I think the only practical way of obtaining this information is to
>> > add eassert's that will tell you which one is it.
>> But I don't know what to add where, at this point.
> Maybe I misunderstood.  You said:
>> It might also be interesting to look at `i' to see whether it's
>> hopelessly messed up, or if it looks "incorrect but sanish".
> So I thought about an eassert that will catch something "hopelessly
> messed up", for example.

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".


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

Previous Next

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