From: Alexis <flexibeast@gmail.com>
To: emacs-devel@gnu.org
Cc: dmantipov@yandex.ru
Subject: Emacs daemon segfaults [was: Possible bug when running with --daemon on 24.3.92.3?]
Date: Fri, 11 Jul 2014 14:51:29 +1000 [thread overview]
Message-ID: <87mwcgv5u0.fsf@gmail.com> (raw)
In-Reply-To: <ksy4w1h3b0.fsf@netfonds.no>
Peder O. Klingenberg writes:
> On Thu, Jul 10 2014 at 09:41, Alexis wrote:
>
>> Peder O. Klingenberg writes:
>>
>>> Try attaching gdb to the emacs process before starting the
>>> emacsclient, and see if you catch a signal as you exit emacsclient?
>>
>> When i enter C-x 5 0 in emacsclient, gdb reports:
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> PSEUDOVECTORP (code=15, a=536871013) at lisp.h:2436
>> 2436 return PSEUDOVECTOR_TYPEP (h, code);
>
> So your emacs dies with a segfault, same as mine did. But not on the
> same line (or perhaps there's been code changes in that area since
> march, I haven't checked). WRT the Subject of this thread, I'd say
> definitely a bug.
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
It looks like the `font_clear_cache` function was last modified by
Dmitry on 3 March, git commit b0c9db81.
i tried `next`ing through that function for a while[1], and at one point
started getting values for the `entity' variable such as -16777216 and
16777215, which look suspiciously like a 24-bit-related issue to this
untrained eye .... The last value of the `entity` variable i got before
the segfault was 536871013.
Does anyone have any advice as to how i can proceed further?
Alexis.
[1] Not fully, because i didn't know the value of `ASIZE (elt)`, since
according to GDB it had been optimized out, despite me `make`ing the
binary with `-O0 -g3`, as per etc/DEBUG (i'm running gcc 4.7.2).
next prev parent reply other threads:[~2014-07-11 4:51 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 [this message]
2014-07-11 8:01 ` Dmitry Antipov
2014-07-11 8:27 ` Alexis
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=87mwcgv5u0.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=dmantipov@yandex.ru \
--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).