unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexis <flexibeast@gmail.com>
To: emacs-devel@gnu.org
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	[thread overview]
Message-ID: <87k37kuwkb.fsf@gmail.com> (raw)
In-Reply-To: <53BF99D7.3040200@yandex.ru>


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, driver=driver@entry=0xb7b6e0, 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, driver=driver@entry=0xb7b6e0, 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 (f=f@entry=0x119d858, 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, nargs=nargs@entry=1, arg_vector=0x10ac1d0, arg_vector@entry=0x7fffa4a0e4a8) 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, nargs=nargs@entry=1, arg_vector=0x10ba390, arg_vector@entry=0x7fffa4a0e5d8) 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, nargs=nargs@entry=1, arg_vector=0x8adf30, arg_vector@entry=0x7fffa4a0e728) at eval.c:2983
#14 0x000000000055c123 in Ffuncall (nargs=nargs@entry=2, args=args@entry=0x7fffa4a0e720) 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, nargs=nargs@entry=1, arg_vector=0x91c330, arg_vector@entry=0x7fffa4a0e9e8) at eval.c:2983
#19 0x000000000055c123 in Ffuncall (nargs=nargs@entry=2, args=args@entry=0x7fffa4a0e9e0) 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 (bfun=bfun@entry=0x4f6ba0 <command_loop_1>, handlers=<optimized out>, hfun=hfun@entry=0x4edc70 <cmd_error>) at eval.c:1354
#23 0x00000000004eb76e in command_loop_2 (ignore=ignore@entry=12100466) at keyboard.c:1177
#24 0x000000000055a5db in internal_catch (tag=12147682, func=func@entry=0x4eb750 <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.



  reply	other threads:[~2014-07-11  8:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  7:30 Possible bug when running with --daemon on 24.3.92.3? Alexis
2014-07-08  8:30 ` Stephen J. Turnbull
2014-07-08  8:53   ` Andreas Schwab
2014-07-08  9:33   ` Alexis
2014-07-08 17:28     ` David Kastrup
2014-07-09  1:11       ` Alexis
2014-07-08 14:57   ` Eli Zaretskii
2014-07-09  7:23 ` Peder O. Klingenberg
2014-07-10  7:41   ` Alexis
2014-07-10 11:16     ` Peder O. Klingenberg
2014-07-11  1:25       ` Emacs daemon segfaults [was: Possible bug when running with --daemon on 24.3.92.3?] Alexis
2014-07-11  4:51       ` Alexis
2014-07-11  8:01         ` Dmitry Antipov
2014-07-11  8:27           ` Alexis [this message]
2014-07-11  8:02         ` Peder O. Klingenberg
2014-07-11  8:45           ` Alexis
2014-07-11  8:57           ` Alexis
2014-07-10 20:59   ` Possible bug when running with --daemon on 24.3.92.3? Michael Mattie
2014-07-11  1:22     ` Alexis

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=87k37kuwkb.fsf@gmail.com \
    --to=flexibeast@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).