From: Kenichi Handa <handa@m17n.org>
To: Kenichi Handa <handa@ni.aist.go.jp>
Cc: wence@gmx.li, dann@ics.uci.edu, emacs-pretest-bug@gnu.org
Subject: Re: --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient)
Date: Sun, 17 Feb 2008 18:24:23 +0900 [thread overview]
Message-ID: <E1JQfl1-0001Kc-Vf@etlken.m17n.org> (raw)
In-Reply-To: <E1JPGwe-0007Bj-Oc@etlken.m17n.org> (message from Kenichi Handa on Wed, 13 Feb 2008 21:42:36 +0900)
In article <E1JPGwe-0007Bj-Oc@etlken.m17n.org>, Kenichi Handa <handa@ni.aist.go.jp> writes:
> In article <200802061528.m16FSb4C026474@sallyv1.ics.uci.edu>, Dan Nicolaescu <dann@ics.uci.edu> writes:
> > Does this backtrace (from an up to date build) help?
> > (gdb) bt
> > #0 0x005ed0a0 in _xcb_unlock_io () from /usr/lib/libxcb.so.1
> > #1 0x005c9649 in xcb_xlib_lock () from /usr/lib/libxcb-xlib.so.0
> > #2 0x00644a56 in ?? () from /usr/lib/libX11.so.6
> > #3 0x0064518c in _XReply () from /usr/lib/libX11.so.6
> > #4 0x00638eaa in XSync () from /usr/lib/libX11.so.6
> > #5 0x080d7a7d in x_catch_errors (dpy=0x8686890)
> > at /tmp/emacs/src/xterm.c:7859
> > #6 0x080db19d in x_connection_closed (dpy=0x8686890,
> > error_message=0xbfebc758 "X protocol error: BadFont (invalid Font parameter) on protocol request 55") at /tmp/emacs/src/xterm.c:8017
> [...]
> Yes, thank you. I found what is wrong, but the fix needs
> more time. Please wait.
I installed some fixes. With the new code, the emacs
configured with '--with-x-toolkit=lucid
--enable-font-backend' works.
But, if I configured emacs to use Gtk, emacsclient causes
segfault as this:
(gdb) bt
#0 0xb78cf727 in XFreeGC () from /usr/X11R6/lib/libX11.so.6
#1 0xb7c728be in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#2 0x00000000 in ?? ()
Lisp Backtrace:
"delete-frame" (0xbfdb6ae4)
"call-interactively" (0xbfdb6d44)
and it's reproducable with the emacs before unicode merge.
On this system, the version of Gtk+ is 2.6.4.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-02-17 9:24 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 ` --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient) Dan Nicolaescu
2008-02-05 7:43 ` 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 ` Kenichi Handa [this message]
2008-02-17 15:48 ` --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient) 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=E1JQfl1-0001Kc-Vf@etlken.m17n.org \
--to=handa@m17n.org \
--cc=dann@ics.uci.edu \
--cc=emacs-pretest-bug@gnu.org \
--cc=handa@ni.aist.go.jp \
--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).