From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: yair.f.lists@gmail.com, 6621@debbugs.gnu.org
Subject: bug#6621: Emacs crash when trying to report emacs crash
Date: Fri, 16 Jul 2010 15:00:14 +0900 [thread overview]
Message-ID: <tl7hbk00xw1.fsf@m17n.org> (raw)
In-Reply-To: <83k4oxhk1c.fsf@gnu.org> (message from Eli Zaretskii on Wed, 14 Jul 2010 23:42:55 +0300)
In article <83k4oxhk1c.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> > Date: Wed, 14 Jul 2010 20:54:33 +0300
> > From: Yair F <yair.f.lists@gmail.com>
> > Cc: handa@m17n.org, 6621@debbugs.gnu.org
> >
> > > My Emacs is not compiled with -DENABLE_CHECKING, so the assert
> > > triggered here is a no-op for me, and Emacs works for me just fine
> > > with this recipe.
> > I have a slight suspicion that this relates to OTF/XFT font handling.
> > You build on Windows right?
> Yes.
> > > Finally, does the problem persist if you turn off
> > > auto-composition-mode before pasting the text?
> > As expected, turning off auto-composition-mode prevents the crash.
> Handa-san, could you take a look at this crash, please?
Unfortunately, I can't reproduce the crash, but anyway, I've
just started to investigate what is wrong.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2010-07-16 6:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 21:55 bug#6621: Emacs crash when trying to report emacs crash Yair F
2010-07-13 12:17 ` Eli Zaretskii
2010-07-13 16:15 ` Yair F
2010-07-13 17:57 ` Eli Zaretskii
2010-07-13 18:29 ` Yair F
2010-07-14 8:32 ` Eli Zaretskii
2010-07-14 11:10 ` Eli Zaretskii
2010-07-14 17:54 ` Yair F
2010-07-14 20:42 ` Eli Zaretskii
2010-07-16 6:00 ` Kenichi Handa [this message]
2010-07-22 19:55 ` Yair F
2010-07-23 12:38 ` Kenichi Handa
2010-07-24 22:05 ` Yair F
2010-07-26 4:30 ` Kenichi Handa
2010-07-26 10:12 ` Juanma Barranquero
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=tl7hbk00xw1.fsf@m17n.org \
--to=handa@m17n.org \
--cc=6621@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=yair.f.lists@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.