From: Dan Nicolaescu <dann@ics.uci.edu>
To: Lawrence Mitchell <wence@gmx.li>
Cc: emacs-pretest-bug@gnu.org
Subject: --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient)
Date: Mon, 04 Feb 2008 16:18:53 -0800 [thread overview]
Message-ID: <200802050018.m150IrgE007563@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <?fnord?y3h6tzko8xsl.fsf@ID-97657.user.individual.net> (Lawrence Mitchell's message of "Mon, 04 Feb 2008 16:57:14 +0000")
Lawrence Mitchell <wence@gmx.li> writes:
> Please describe exactly what actions triggered the bug
> and the precise symptoms of the bug:
>
> The following sequence of events causes Emacs to segfault
> somewhere in x-create-frame.
>
> Run emacs in a terminal
>
> 1) emacs -nw -Q --eval '(server-start)'
>
> Create an X frame.
> 2) emacsclient -c -d :0.0
>
> Delete the frame
> 3) C-x 5 0
>
> Try and create another X frame.
> 4) emacsclient -c -d :0.0
>
> leading to the following backtrace:
I don't get a segfault, but emacs and emacsclient hang.
It only happens when configuring with --enable-font-backend, it works
fine without that flag.
next prev parent reply other threads:[~2008-02-05 0:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 16:57 23.0.60; emacs segfaults when creating X display via emacsclient Lawrence Mitchell
2008-02-04 20:17 ` Lawrence Mitchell
2008-02-05 0:18 ` Dan Nicolaescu [this message]
2008-02-05 7:43 ` --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient) Kenichi Handa
2008-02-05 8:15 ` Dan Nicolaescu
2008-02-05 11:22 ` Kenichi Handa
2008-02-05 13:57 ` Dan Nicolaescu
2008-02-06 0:55 ` Kenichi Handa
2008-02-06 2:36 ` Nick Roberts
2008-02-06 15:28 ` Dan Nicolaescu
2008-02-13 12:42 ` Kenichi Handa
2008-02-13 13:38 ` --enable-font-backend bug Leo
2008-02-17 9:24 ` --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient) Kenichi Handa
2008-02-17 15:48 ` Dan Nicolaescu
2008-02-18 11:01 ` 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
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=200802050018.m150IrgE007563@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-pretest-bug@gnu.org \
--cc=wence@gmx.li \
/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).