From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: lekktu@gmail.com, 5984@debbugs.gnu.org
Subject: bug#5984: Crash displaying composed characters
Date: Fri, 23 Apr 2010 12:17:57 +0300 [thread overview]
Message-ID: <83vdbi34u2.fsf@gnu.org> (raw)
In-Reply-To: <m24oj5dlxk.fsf@igel.home>
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, 5984@debbugs.gnu.org
> Date: Wed, 21 Apr 2010 14:33:59 +0200
>
> Juanma Barranquero <lekktu@gmail.com> writes:
>
> >> Please try this patch.
> >
> > With it, I don't get a crash, but an error:
> >
> > Wrong type argument: bufferp, 12846208
>
> Here's an updated patch.
Thanks. This prevents the crash, but the message shown in the echo
area is "Loading lisp/international/uni-combining.el (source)...done",
whereas I would expect to see the message from Edebug saying
"Result: ...", as if uni-combining.el was never loaded.
If this is hard to do, then perhaps we should install this patch on
the Emacs 23 branch, and enhance it later on the trunk to show the
Edebug message.
next prev parent reply other threads:[~2010-04-23 9:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 13:42 bug#5984: Crash displaying composed characters Juanma Barranquero
2010-04-20 15:06 ` Eli Zaretskii
2010-04-20 15:48 ` Juanma Barranquero
2010-04-20 16:07 ` Eli Zaretskii
2010-04-20 18:38 ` Glenn Morris
2010-04-20 17:29 ` Eli Zaretskii
2010-04-20 17:33 ` Juanma Barranquero
2010-04-20 17:52 ` Eli Zaretskii
2010-04-20 18:43 ` Lennart Borgman
2010-04-20 19:18 ` Eli Zaretskii
2010-04-20 20:38 ` Andreas Schwab
2010-04-21 10:48 ` Juanma Barranquero
2010-04-21 12:33 ` Andreas Schwab
2010-04-21 17:21 ` Juanma Barranquero
2010-04-23 9:17 ` Eli Zaretskii [this message]
2011-07-06 2:28 ` Juanma Barranquero
2011-08-07 19:45 ` Chong Yidong
2011-11-23 3:14 ` Juanma Barranquero
2011-11-23 6:47 ` Chong Yidong
2010-04-30 20:47 ` Stefan Monnier
2010-05-01 6:09 ` Eli Zaretskii
2010-05-01 6:28 ` Kenichi Handa
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=83vdbi34u2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=5984@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=schwab@linux-m68k.org \
/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.