[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17411: 24.4.50; emacs_backtrace.txt
From: |
Stefan Monnier |
Subject: |
bug#17411: 24.4.50; emacs_backtrace.txt |
Date: |
Tue, 13 May 2014 15:32:13 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) |
>> > 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
- bug#17411: 24.4.50; emacs_backtrace.txt, Drew Adams, 2014/05/05
- bug#17411: 24.4.50; emacs_backtrace.txt, Juanma Barranquero, 2014/05/07
- bug#17411: 24.4.50; emacs_backtrace.txt, Eli Zaretskii, 2014/05/11
- bug#17411: 24.4.50; emacs_backtrace.txt, Stefan Monnier, 2014/05/11
- bug#17411: 24.4.50; emacs_backtrace.txt, Eli Zaretskii, 2014/05/12
- bug#17411: 24.4.50; emacs_backtrace.txt, Stefan Monnier, 2014/05/12
- bug#17411: 24.4.50; emacs_backtrace.txt, Eli Zaretskii, 2014/05/12
- bug#17411: 24.4.50; emacs_backtrace.txt,
Stefan Monnier <=
- bug#17411: 24.4.50; emacs_backtrace.txt, Eli Zaretskii, 2014/05/13
- bug#17411: 24.4.50; emacs_backtrace.txt, Stefan Monnier, 2014/05/13
- bug#17411: 24.4.50; emacs_backtrace.txt, Eli Zaretskii, 2014/05/13
- bug#17411: 24.4.50; emacs_backtrace.txt, Stefan Monnier, 2014/05/13
- bug#17411: 24.4.50; emacs_backtrace.txt, Drew Adams, 2014/05/14
- bug#17411: 24.4.50; emacs_backtrace.txt, Eli Zaretskii, 2014/05/14