From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: david.reitter@gmail.com, 5973@debbugs.gnu.org
Subject: bug#5973: Crash in get_next_display_element
Date: Tue, 20 Apr 2010 12:56:09 +0300 [thread overview]
Message-ID: <83d3xu5txi.fsf@gnu.org> (raw)
In-Reply-To: <o2zf7ccd24b1004200219ree5945b3l47c18698d2a06782@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Tue, 20 Apr 2010 11:19:44 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, david.reitter@gmail.com, 5973@debbugs.gnu.org
>
> I was debugging a simple defadvice to narrow-to-region. The "text" of
> the message is edebug trying to display END (the argument to n-t-r). I
> can reproduce the bug with just this advice:
>
> (defadvice narrow-to-region (before heisenbug activate)
> end)
>
> I instrument it with C-u C-M-x
Instrument what? the defadvice, or something else?
> then C-h N to show NEWS, select a few lines and C-x n n.
Which lines did you select? I think this is important, because
when a form is evaluated, Edebug displays in the echo area a message
showing the result of the evaluation, and if the result is a number,
it tries to display it as a character. So the end of the region you
select determines what character will Edebug try to display.
> I get a message "Loading c:/emacs/lisp/international/uni-category.el
> (source)...done" and then the crash.
I don't see this message, perhaps because I used a different region.
I see all kinds of characters displayed, depending on what region I
select, but no crash. Here's one example
Result: 784 (#o1420, #x310, ?̐)
I'm guessing that the crash is somehow related to display of composite
characters (hint: try "C-u C-x =" on the weirdo question mark above),
which the bidi display does not handle correctly yet.
next prev parent reply other threads:[~2010-04-20 9:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 16:08 bug#5973: Crash in get_next_display_element David Reitter
[not found] ` <handler.5973.B.12716933351499.ack@debbugs.gnu.org>
2010-04-19 16:46 ` bug#5973: Acknowledgement (Crash in get_next_display_element) David Reitter
2010-04-19 17:31 ` Eli Zaretskii
2010-04-19 17:23 ` bug#5973: Crash in get_next_display_element Eli Zaretskii
2010-04-19 17:40 ` David Reitter
2010-04-19 18:26 ` Eli Zaretskii
2010-04-19 18:39 ` David Reitter
2010-04-19 18:43 ` Eli Zaretskii
2010-04-19 22:46 ` Juanma Barranquero
2010-04-20 8:23 ` Eli Zaretskii
2010-04-20 9:19 ` Juanma Barranquero
2010-04-20 9:56 ` Eli Zaretskii [this message]
2010-04-20 10:27 ` Juanma Barranquero
2010-04-20 12:31 ` Eli Zaretskii
2010-04-20 13:36 ` Juanma Barranquero
2010-04-20 13:56 ` Juanma Barranquero
2010-04-20 10:21 ` Eli Zaretskii
2010-04-20 10:33 ` Juanma Barranquero
2010-04-20 12:23 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d3xu5txi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=5973@debbugs.gnu.org \
--cc=david.reitter@gmail.com \
--cc=lekktu@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.