Re: Segfault in Emacs 23 with multi-tty

[Daniel Hackney]

On 12/12/07, Daniel Hackney <dan@haxney.org> wrote:
> I tried the current emacs-unicode-2 branch which I got using git from
> git://git.sv.gnu.org/emacs.git, using the commit
> 65a977059896b030055ff2b39513c32962519b6b. I compiled with
>
>  $ ./configure --prefix=/home/frochild/Projects/emacs-bin --with-gtk
> --with-xft CFLAGS="-O0 -g"
>
> as recommended.
>
> It did not segfault, but when closing the GTK window, the following was 
> written
> to stderr of the server instance:
>
> -- SNIP --

I tried again with the font server, and did get it to segfault. This time I
configured with

 $ ./configure --prefix=/home/frochild/Projects/emacs-bin --with-gtk
--with-xft CFLAGS="-O0 -g" --enable-font-backend

And ran the server with

 $ emacs -q -nw --eval "(setq server-name \"editor\")" -f server-start
 --enable-font-backend

And the client with:

 $ emacsclient -s editor -c

It opened a window successfully, but when I ran "save-buffers-kill-terminal",
the server died with the following backtrace:

(gdb) where
#0  0x081183e3 in x_delete_terminal (terminal=0x8526838) at xterm.c:11721
#1  0x08063e60 in Fdelete_frame (frame=147149636, force=138254537) at
frame.c:1538
#2  0x081d954b in Ffuncall (nargs=2, args=0xbfe7cb50) at eval.c:3027
#3  0x0821322e in Fbyte_code (bytestr=143782139, vector=146664764,
maxdepth=48) at bytecode.c:679
#4  0x081d9d24 in funcall_lambda (fun=141123292, nargs=1,
arg_vector=0xbfe7ce84) at eval.c:3211
#5  0x081d97b3 in Ffuncall (nargs=2, args=0xbfe7ce80) at eval.c:3070
#6  0x0821322e in Fbyte_code (bytestr=144008315, vector=144391396,
maxdepth=24) at bytecode.c:679
#7  0x081d9d24 in funcall_lambda (fun=145145876, nargs=2,
arg_vector=0xbfe7d1a4) at eval.c:3211
#8  0x081d97b3 in Ffuncall (nargs=3, args=0xbfe7d1a0) at eval.c:3070
#9  0x0821322e in Fbyte_code (bytestr=136936147, vector=136936164,
maxdepth=32) at bytecode.c:679
#10 0x081d9d24 in funcall_lambda (fun=136936100, nargs=1,
arg_vector=0xbfe7d514) at eval.c:3211
#11 0x081d97b3 in Ffuncall (nargs=2, args=0xbfe7d510) at eval.c:3070
#12 0x081d4e87 in Fcall_interactively (function=143574953,
record_flag=138254537, keys=138292956)
    at callint.c:841
#13 0x0815ac87 in Fcommand_execute (cmd=143574953,
record_flag=138254537, keys=138254537,
    special=138254537) at keyboard.c:10479
#14 0x0814c0b0 in command_loop_1 () at keyboard.c:1941
#15 0x081d6ff2 in internal_condition_case (bfun=0x814a915
<command_loop_1>, handlers=138298769,
    hfun=0x814a2b9 <cmd_error>) at eval.c:1493
#16 0x0814a66e in command_loop_2 () at keyboard.c:1398
#17 0x081d6ad8 in internal_catch (tag=138293617, func=0x814a64b
<command_loop_2>, arg=138254537)
    at eval.c:1229
#18 0x0814a624 in command_loop () at keyboard.c:1377
#19 0x08149ec6 in recursive_edit_1 () at keyboard.c:986
#20 0x0814a034 in Frecursive_edit () at keyboard.c:1048
#21 0x081488a7 in main (argc=8, argv=0xbfe7e034) at emacs.c:1808

Hopefully this is a more useful backtrace. The same thing happened if Emacs was
launched without "--enable-font-backend", so it seems to be a problem with
the configure flag.

-- 
Daniel M. Hackney