[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs daemon segfaults [was: Possible bug when running with --daemon
From: |
Alexis |
Subject: |
Re: Emacs daemon segfaults [was: Possible bug when running with --daemon on 24.3.92.3?] |
Date: |
Fri, 11 Jul 2014 18:27:59 +1000 |
Dmitry Antipov writes:
> On 07/11/2014 08:51 AM, Alexis wrote:
>
>> Well, getting a backtrace produced:
>>
>> #0 PSEUDOVECTORP (code=15, a=536871013) at lisp.h:2436
>> #1 font_clear_cache (cache=15546662, address@hidden, f=<error reading
>> variable: Unhandled dwarf expression opcode 0xfa>) at font.c:2607
>
> Please send the backtrace with all stack frames.
Program received signal SIGSEGV, Segmentation fault.
PSEUDOVECTORP (code=15, a=536871013) at lisp.h:2436
2436 return PSEUDOVECTOR_TYPEP (h, code);
(gdb) backtrace
#0 PSEUDOVECTORP (code=15, a=536871013) at lisp.h:2436
#1 font_clear_cache (cache=15546662, address@hidden, f=<error reading
variable: Unhandled dwarf expression opcode 0xfa>) at font.c:2607
#2 0x000000000056f990 in font_finish_cache (driver=0xb7b6e0, f=0x119d858) at
font.c:2566
#3 font_update_drivers (address@hidden, new_drivers=12100466) at font.c:3475
#4 0x0000000000426d84 in delete_frame (frame=<optimized out>, force=12100466)
at frame.c:1335
#5 0x000000000055c338 in Ffuncall (nargs=<optimized out>, args=<optimized
out>) at eval.c:2818
#6 0x000000000059077d in exec_byte_code (bytestr=5, vector=12039904,
maxdepth=4611686018679046144, args_template=2052, nargs=142, args=0x2) at
bytecode.c:916
#7 0x000000000055be57 in funcall_lambda (fun=140735955395408, address@hidden,
arg_vector=0x10ac1d0, address@hidden) at eval.c:2983
#8 0x000000000055c123 in Ffuncall (nargs=2, args=0x7fffa4a0e4a0) at eval.c:2876
#9 0x000000000059077d in exec_byte_code (bytestr=5, vector=12039904,
maxdepth=4611686018679046144, args_template=1028, nargs=63, args=0x2) at
bytecode.c:916
#10 0x000000000055be57 in funcall_lambda (fun=140735955395744, address@hidden,
arg_vector=0x10ba390, address@hidden) at eval.c:2983
#11 0x000000000055c123 in Ffuncall (nargs=2, args=0x7fffa4a0e5d0) at eval.c:2876
#12 0x000000000059077d in exec_byte_code (bytestr=5, vector=12039904,
maxdepth=4611686018679046144, args_template=1024, nargs=11, args=0x2) at
bytecode.c:916
#13 0x000000000055be57 in funcall_lambda (fun=140735955396048, address@hidden,
arg_vector=0x8adf30, address@hidden) at eval.c:2983
#14 0x000000000055c123 in Ffuncall (address@hidden, address@hidden) at
eval.c:2876
#15 0x00000000005586dd in Fcall_interactively (function=16364402,
record_flag=12100466, keys=12135165) at callint.c:836
#16 0x000000000055c328 in Ffuncall (nargs=<optimized out>, args=<optimized
out>) at eval.c:2822
#17 0x000000000059077d in exec_byte_code (bytestr=5, vector=12039904,
maxdepth=4611686018679046144, args_template=4100, nargs=108, args=0x4) at
bytecode.c:916
#18 0x000000000055be57 in funcall_lambda (fun=140735955396808, address@hidden,
arg_vector=0x91c330, address@hidden) at eval.c:2983
#19 0x000000000055c123 in Ffuncall (address@hidden, address@hidden) at
eval.c:2876
#20 0x000000000055c4fa in call1 (fn=<optimized out>, arg1=<optimized out>) at
eval.c:2614
#21 0x00000000004f6f2e in command_loop_1 () at keyboard.c:1559
#22 0x000000000055a6d5 in internal_condition_case (address@hidden
<command_loop_1>, handlers=<optimized out>, address@hidden <cmd_error>) at
eval.c:1354
#23 0x00000000004eb76e in command_loop_2 (address@hidden) at keyboard.c:1177
#24 0x000000000055a5db in internal_catch (tag=12147682, address@hidden
<command_loop_2>, arg=12100466) at eval.c:1118
#25 0x00000000004ed877 in command_loop () at keyboard.c:1156
#26 recursive_edit_1 () at keyboard.c:777
#27 0x00000000004edb8d in Frecursive_edit () at keyboard.c:848
#28 0x00000000004196c5 in main (argc=3, argv=<optimized out>) at emacs.c:1646
Lisp Backtrace:
"delete-frame" (0xa4a0e358)
"server-delete-client" (0xa4a0e4a8)
"server-save-buffers-kill-terminal" (0xa4a0e5d8)
"save-buffers-kill-terminal" (0xa4a0e728)
"call-interactively" (0xa4a0e8d0)
"command-execute" (0xa4a0e9e8)
> Also note that original recipe, i.e.
>
> 1. emacs -q --daemon
> 2. emacsclient -c
> 3. C-x C-c
> 4. The `emacs --daemon` process is no longer running.
>
> doesn't work for me (daemon is still alive after closing the frame).
*nod* This issue has only appeared for me on 64-bit Debian Wheezy, not
on the 32-bit version.
Alexis.
- Re: Possible bug when running with --daemon on 24.3.92.3?, (continued)
Re: Possible bug when running with --daemon on 24.3.92.3?, Peder O. Klingenberg, 2014/07/10
Re: Possible bug when running with --daemon on 24.3.92.3?, Michael Mattie, 2014/07/10
Re: Possible bug when running with --daemon on 24.3.92.3?, Kelvin White, 2014/07/10