all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: James Cloos <cloos@jhcloos.com>
Cc: emacs-pretest-bug@gnu.org, handa@m17n.org
Subject: Re: 23.0.60; SEGV in font_score()
Date: Sun, 08 Jun 2008 20:25:31 +0900	[thread overview]
Message-ID: <E1K5J1f-0007NK-LA@etlken.m17n.org> (raw)
In-Reply-To: <m3k5h1cc6m.fsf@lugabout.jhcloos.org> (message from James Cloos on Sat, 07 Jun 2008 14:49:30 -0400)

In article <m3k5h1cc6m.fsf@lugabout.jhcloos.org>, James Cloos <cloos@jhcloos.com> writes:

> Compiled again, this time w/o -O2.
> With -O2 entity got optimized out, so the crash was reported on line
> 1990:

>         if (xstrcasecmp (SDATA (spec_str), SDATA (entity_str)))

> but w/o -O2 it occurs a couple of lines up at:

>         Lisp_Object entity_str = SYMBOL_NAME (AREF (entity, i));

Ah.

> Since I can only trigger this randomly while reading mail with gnus, and
> since nnimap takes about an hour to start up, this is very fustrating to
> debug.

> I was able to convince the xpr macro in gdb to tell me that the first
> element of entity is "xft",

Hmmm, then it seems that at least entity is a correct
font-entity object.  So, perhaps the 2nd element (you wrote
that `i' was 2) of it was set to something other than symbol.

> but I couldn't figure out how to get to the
> next element.

I've just installed a new gdb function xfont of .gdbinit.
With that, you can do something like this:

(gdb) p entity
$1 = 147592732
(gdb) xfont
$2 = (struct font_entity *) 0x8cc1618
(gdb) p $2->props[FONT_FAMILY_INDEX]
$3 = 148609265
(gdb) xtype
Lisp_Symbol

> Handa-san: I can provide a -ggdb core dump off list.  It looks to have
> much more value than the dump I mentioned in the initial bug report.
> (It is quite large, though.  More than 64 Megs uncompressed.)

I think that kind of dump doesn't help that much because the
problem is in Lisp object.  If you still keep that gdb
session, please try above (after you get the new .gdbinit
from the CVS repository, and do "(gdb) source .gdbinit").
 
And also this will help.

(gdb) up 2
#2  0x081e64d7 in font_find_for_lface (f=0x84e5300, attrs=0x89ea6f8, spec=147460412, c=-1) at font.c:2893
(gdb) pr spec
(gdb) pr prefer

---
Kenichi Handa
handa@ni.aist.go.jp




  reply	other threads:[~2008-06-08 11:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 22:20 23.0.60; SEGV in font_score() James Cloos
2008-06-05  5:58 ` Kenichi Handa
2008-06-05 18:16   ` James Cloos
2008-06-06  5:48   ` James Cloos
2008-06-06 21:08     ` James Cloos
2008-06-07 18:49       ` James Cloos
2008-06-08 11:25         ` Kenichi Handa [this message]
2008-06-08 18:54           ` James Cloos
2008-06-09 20:08             ` James Cloos
2008-06-10  2:09               ` 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=E1K5J1f-0007NK-LA@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=cloos@jhcloos.com \
    --cc=emacs-pretest-bug@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.