From: Werner LEMBERG <wl@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs crash CVS 2003-10-17
Date: Mon, 10 Nov 2003 14:54:06 +0100 (CET) [thread overview]
Message-ID: <20031110.145406.63054872.wl@gnu.org> (raw)
In-Reply-To: <200311101142.UAA29631@etlken.m17n.org>
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x08077c43 in fill_glyph_string (s=0xbfffe424, face_id=26,
> > start=6, end=79, overlaps_p=0) at xdisp.c:16730
> > 16730 = FONT_INFO_FROM_ID (f, face->font_info_id);
>
> I'd like to know the result of these:
> (gdb) p *face
> (gdb) p *glyph
(gdb) p *face
Cannot access memory at address 0x0
(gdb) p *glyph
$5 = {
charpos = 7,
object = -2006738280,
pixel_width = 24,
voffset = 0,
type = 0,
multibyte_p = 1,
left_box_line_p = 0,
right_box_line_p = 0,
overlaps_vertically_p = 0,
padding_p = 0,
glyph_not_available_p = 0,
face_id = 26,
font_type = 0,
u = {
ch = 157926,
cmp_id = 157926,
img_id = 157926,
stretch = {
height = 26854,
ascent = 2
},
val = 157926
}
}
> But, as it crashes in the inline function
> get_glyph_face_and_encoding, those values won't be available in the
> current gdb session.
>
> Can you reproduce it constantly?
No.
> If not, could you
> re-compile xdisp.c with CFLAGS='-g -fno-inline', rebuild
> emacs, and use it for a while? The actual procedure will
> be:
> % cd .../emacs/src
> % rm xdisp.o
> % make CFLAGS='-g -fno-inline'
OK, I'll rebuild emacs from a recent CVS snapshot with `-O0'.
Werner
next prev parent reply other threads:[~2003-11-10 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 8:36 Emacs crash CVS 2003-10-17 Werner LEMBERG
2003-11-10 11:42 ` Kenichi Handa
2003-11-10 13:54 ` Werner LEMBERG [this message]
2003-11-11 0:15 ` Kenichi Handa
2003-11-11 5:29 ` Werner LEMBERG
2003-11-11 11:09 ` Kenichi Handa
2003-11-12 15:05 ` Werner LEMBERG
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=20031110.145406.63054872.wl@gnu.org \
--to=wl@gnu.org \
--cc=emacs-devel@gnu.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.