From: Jason Rumney <jasonr@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs- devel <emacs-devel@gnu.org>
Subject: Re: segmentation fault displaying etc/HELLO on Windows
Date: Wed, 30 Jul 2008 07:48:50 +0100 [thread overview]
Message-ID: <48900ED2.2000703@gnu.org> (raw)
In-Reply-To: <f7ccd24b0807291349r5c16ca53gee0a4229ac9f9b8e@mail.gmail.com>
Juanma Barranquero wrote:
> However, C-h H crashes Emacs:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x011ea1ff in w32_compute_glyph_string_overhangs (s=0x82eaf0) at w32term.c:1194
> 1194 font->driver->text_extents (font, code, s->nchars, &metrics);
> (gdb) bt
> #0 0x011ea1ff in w32_compute_glyph_string_overhangs (s=0x82eaf0) at
> w32term.c:1194
That seems to suggest that s->font is invalid, but s->font_not_found_p
is not set. Can you see what characters are being drawn here
(s->first_glyph->u.ch) so you can narrow down which font should be being
used (based on earlier versions) and start stepping through the code
earlier (use a conditional breakpoint based on the character being
displayed).
next prev parent reply other threads:[~2008-07-30 6:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 20:49 segmentation fault displaying etc/HELLO on Windows Juanma Barranquero
2008-07-30 6:48 ` Jason Rumney [this message]
2008-07-30 11:48 ` Juanma Barranquero
2008-07-30 13:05 ` Jason Rumney
2008-07-30 13:11 ` Jason Rumney
2008-07-30 14:03 ` Juanma Barranquero
2008-07-30 14:19 ` Choice of fonts displaying etc/HELLO (was: Re: segmentation fault displaying etc/HELLO on Windows) Jason Rumney
2008-07-30 15:03 ` Choice of fonts displaying etc/HELLO Jason Rumney
2008-07-30 15:26 ` Juanma Barranquero
2008-08-01 12:50 ` Kenichi Handa
2008-08-01 12:56 ` Choice of fonts displaying etc/HELLO (was: Re: segmentation fault displaying etc/HELLO on Windows) Kenichi Handa
2008-08-01 13:17 ` Choice of fonts displaying etc/HELLO Jason Rumney
2008-08-01 13:51 ` Eli Zaretskii
2008-08-05 7:33 ` Kenichi Handa
2008-08-05 18:12 ` Eli Zaretskii
2008-08-06 5:30 ` Kenichi Handa
2008-08-06 6:14 ` Stephen J. Turnbull
2008-08-06 6:29 ` Kenichi Handa
2008-08-06 15:52 ` Stephen J. Turnbull
2008-08-06 17:56 ` Eli Zaretskii
2008-08-07 1:14 ` Kenichi Handa
2008-08-07 3:22 ` Eli Zaretskii
2008-08-07 3:54 ` Kenichi Handa
2008-08-07 4:54 ` Miles Bader
2008-08-07 18:03 ` Eli Zaretskii
2008-08-07 19:30 ` Stephen J. Turnbull
2008-08-11 8:48 ` Miles Bader
2008-08-11 19:03 ` Eli Zaretskii
2008-07-31 1:49 ` segmentation fault displaying etc/HELLO on Windows Kyle M. Lee
2008-07-31 2:03 ` 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
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=48900ED2.2000703@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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).