From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 9943@debbugs.gnu.org
Subject: bug#9943: 24.0.91; Abort in check_glyph_memory
Date: Thu, 03 Nov 2011 23:59:07 +0200 [thread overview]
Message-ID: <831uton9zo.fsf@gnu.org> (raw)
In-Reply-To: <4EB30229.7070105@cornell.edu>
> Date: Thu, 03 Nov 2011 17:05:45 -0400
> From: Ken Brown <kbrown@cornell.edu>
> CC: Eli Zaretskii <eliz@gnu.org>, 9943@debbugs.gnu.org
>
> On 11/3/2011 3:58 PM, Glenn Morris wrote:
> > Eli Zaretskii wrote:
> >
> >> I fixed this for w32 (revision 106273 on the trunk). I think the same
> >> problem can happen on X, but I cannot run Emacs on X where I'm typing
> >> this. Could someone please try the recipe on X and see if the same
> >> problem happens there? It could matter which toolkit was used to
> >> build Emacs, so please tell which toolkit you are using. TIA.
> >
> > Lucid toolkit:
>
> [...]
>
> Eli,
>
> I don't know if you need results from a second toolkit, but here's what
> I get with gtk:
>
> (gdb) bt full
> #0 abort () at emacs.c:386
> No locals.
> #1 0x00404781 in check_glyph_memory () at dispnew.c:2370
> tail = 8775706
> frame = -2147299323
> #2 0x005149e8 in shut_down_emacs (sig=0, no_x=0, stuff=8775706)
> at emacs.c:2102
Thanks, I installed a fix.
nsfns.m has a similar problem, but x-create-frame there doesn't have
an unwind-protect function to add a similar change. Can someone test
this recipe on a Mac?
next prev parent reply other threads:[~2011-11-03 21:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 9:17 bug#9943: 24.0.91; Abort in check_glyph_memory martin rudalics
2011-11-03 19:08 ` Eli Zaretskii
2011-11-03 19:58 ` Glenn Morris
2011-11-03 21:05 ` Ken Brown
2011-11-03 21:59 ` Eli Zaretskii [this message]
2011-11-05 12:26 ` Jan Djärv
2011-11-05 13:18 ` Eli Zaretskii
2011-11-05 15:50 ` Jan Djärv
2011-11-05 16:27 ` Eli Zaretskii
2011-11-07 21:05 ` Glenn Morris
2011-11-03 21:57 ` Eli Zaretskii
2011-11-04 0:35 ` Stefan Monnier
2011-11-04 9:12 ` Eli Zaretskii
2011-11-04 16:53 ` Glenn Morris
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=831uton9zo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9943@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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).