From: Richard Hansen <rhansen@bbn.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 3112@emacsbugs.donarmstrong.com
Subject: bug#3112: 23.0.92; segfault in display-supports-face-attributes-p
Date: Thu, 07 May 2009 16:32:17 -0400 [thread overview]
Message-ID: <4A034551.5040201@bbn.com> (raw)
In-Reply-To: <87hc02qlhm.fsf@cyd.mit.edu>
>> I figured out how to reproduce this segfault:
>>
>> Set .emacs to the following:
>>
>> (custom-set-faces
>> '(default ((t (:height 121 :family "something-invalid")))))
>>
>> Then start emacs and let the mouse hover over something that would
>> display a tooltip. After a second or so you'll get the segfault.
>
> I can't reproduce this crash with the recipe you provided. Hovering the
> mouse over the buffer name in the mode-line, or over one of the links in
> the startup screen, displays a tooltip with no crash. I also did
> `xrdb -remove' to clear my X resources---again, no crash with the
> recipe.
My emacs had some Debian-provided patches, so I tried building fresh
from CVS. I'm still having the same problem, and I can still reliably
reproduce the segfault. Here's what I did:
$ cvs -d:pserver:anonymous@cvs.sv.gnu.org:/sources/emacs co emacs
$ cd emacs
$ ./configure
$ make bootstrap
$ make
$ ./src/emacs -Q
Then I evaluated the above snippet and hovered my mouse over something
that produces a tooltip. Presto, instant segfault. If I leave out the
':height 121' from the above snippet, no segfault.
Can anyone else reproduce this?
Thanks,
Richard
next prev parent reply other threads:[~2009-05-07 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 15:01 bug#3112: 23.0.92; segfault in display-supports-face-attributes-p Chong Yidong
2009-05-07 20:32 ` Richard Hansen [this message]
2009-05-08 3:36 ` Chong Yidong
2009-05-09 0:58 ` Stefan Monnier
2009-05-12 20:06 ` Richard Hansen
-- strict thread matches above, loose matches on Subject: below --
2009-04-26 4:39 Richard Hansen
2009-04-28 15:41 ` Richard Hansen
2009-04-28 15:57 ` Richard Hansen
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=4A034551.5040201@bbn.com \
--to=rhansen@bbn.com \
--cc=3112@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.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).