|
From: | Kenichi Handa |
Subject: | Re: --enable-font-backend bug (was: Re: 23.0.60; emacs segfaults when creating X display via emacsclient) |
Date: | Tue, 05 Feb 2008 16:43:19 +0900 |
User-agent: | SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
In article <address@hidden>, Dan Nicolaescu <address@hidden> writes: > 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. As I got "Fatal error (6)Aborted", I started the debugging by running the first emacs under gdb. But I found that I can't suspend it by typing C-z once I did the step 2). Emacs just shows this message: "Suspending an Emacs running under X makes no sense". This makes the debugging very difficult. :-( Is this a multi-tty problem? --- Kenichi Handa address@hidden PS. I had to do this to get this "abort". 1) emacs -nw -Q --eval '(server-start)' 2) emacsclient -c -d :0.0 3) type C-h h 4) C-x 5 0 5) emacsclient -c -d :0.0 6) type C-h h
[Prev in Thread] | Current Thread | [Next in Thread] |