unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: lekktu@gmail.com, 17411@debbugs.gnu.org
Subject: bug#17411: 24.4.50; emacs_backtrace.txt
Date: Tue, 13 May 2014 22:54:08 +0300	[thread overview]
Message-ID: <83bnv1pi8v.fsf@gnu.org> (raw)
In-Reply-To: <jwvmwelschn.fsf-monnier+emacsbugs@gnu.org>

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: lekktu@gmail.com, 17411@debbugs.gnu.org
> Date: Tue, 13 May 2014 15:32:13 -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.





  reply	other threads:[~2014-05-13 19:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 20:08 bug#17411: 24.4.50; emacs_backtrace.txt Drew Adams
2014-05-07 15:20 ` Juanma Barranquero
2014-05-12  2:37   ` Eli Zaretskii
2014-05-12  3:26     ` Stefan Monnier
2014-05-12 13:21       ` Eli Zaretskii
2014-05-12 18:18         ` Stefan Monnier
2014-05-12 18:33           ` Eli Zaretskii
2014-05-13 19:32             ` Stefan Monnier
2014-05-13 19:54               ` Eli Zaretskii [this message]
2014-05-13 21:19                 ` Stefan Monnier
2014-05-14  2:47                   ` Eli Zaretskii
2014-05-14  3:27                     ` Stefan Monnier
2015-12-26 14:16                     ` bug#17340: " Lars Ingebrigtsen
2015-12-26 14:24                       ` Eli Zaretskii
     [not found]                 ` <<jwvbnv1s7jt.fsf-monnier+emacsbugs@gnu.org>
     [not found]                   ` <<837g5poz4o.fsf@gnu.org>
2014-05-14 14:38                     ` Drew Adams
2014-05-14 15:21                       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83bnv1pi8v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17411@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    --cc=monnier@IRO.UMontreal.CA \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).