unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Zack Piper <zack@apertron.net>
To: emacs-devel@gnu.org
Subject: Random segfaults when using M-x.
Date: Fri, 5 Jun 2015 10:20:49 +0000	[thread overview]
Message-ID: <20150605102048.GA31678@apertron.net> (raw)

I get the following backtrace (seemingly at random) when pressing M-x,
this happens sometimes 2 times a day, I didn't report a bug because I
couldn't reproduce it reliably, but it randomly happened 2 times just
now when trying to debug what was happening (both times during trying
to use M-x). Shall I try disecting my Emacs configuration
(https://github.com/zackp30/dotfiles) or wait to see if that's not
needed and it's a known bug?

```
$ sed -n 's/.*\[\(.*\)]$/\1/p' backtrace | addr2line -C -f -i -p -e $(which emacs)
emacs_backtrace at /home/zack/emacs/src/sysdep.c:2188
terminate_due_to_signal at /home/zack/emacs/src/emacs.c:374
handle_fatal_signal at /home/zack/emacs/src/sysdep.c:1604
deliver_thread_signal.constprop.6 at
/home/zack/emacs/src/sysdep.c:1578
handle_sigsegv at /home/zack/emacs/src/sysdep.c:1654
?? ??:0
turn_on_face at /home/zack/emacs/src/term.c:1902 (discriminator 3)
tty_write_glyphs at /home/zack/emacs/src/term.c:777
update_frame_line at /home/zack/emacs/src/dispnew.c:4832
update_frame_1 at /home/zack/emacs/src/dispnew.c:4534
update_frame at /home/zack/emacs/src/dispnew.c:3123
redisplay_internal at /home/zack/emacs/src/xdisp.c:13786
(discriminator 2)
read_char at /home/zack/emacs/src/keyboard.c:2544
read_key_sequence at /home/zack/emacs/src/keyboard.c:9156
command_loop_1 at /home/zack/emacs/src/keyboard.c:1407
internal_condition_case at /home/zack/emacs/src/eval.c:1350
command_loop_2 at /home/zack/emacs/src/keyboard.c:1140 (discriminator
1)
internal_catch at /home/zack/emacs/src/eval.c:1110
command_loop at /home/zack/emacs/src/keyboard.c:1111
recursive_edit_1 at /home/zack/emacs/src/keyboard.c:729
XUNTAG at /home/zack/emacs/src/lisp.h:844
(inlined by) XWINDOW at /home/zack/emacs/src/lisp.h:1010
(inlined by) read_minibuf at /home/zack/emacs/src/minibuf.c:684
Fread_from_minibuffer at /home/zack/emacs/src/minibuf.c:970
Ffuncall at /home/zack/emacs/src/eval.c:2748
exec_byte_code at /home/zack/emacs/src/bytecode.c:919
funcall_lambda at /home/zack/emacs/src/eval.c:2951
backtrace_debug_on_exit at /home/zack/emacs/src/eval.c:159
(inlined by) Ffuncall at /home/zack/emacs/src/eval.c:2791
exec_byte_code at /home/zack/emacs/src/bytecode.c:919
funcall_lambda at /home/zack/emacs/src/eval.c:2951
backtrace_debug_on_exit at /home/zack/emacs/src/eval.c:159
(inlined by) Ffuncall at /home/zack/emacs/src/eval.c:2791
exec_byte_code at /home/zack/emacs/src/bytecode.c:919
funcall_lambda at /home/zack/emacs/src/eval.c:2951
backtrace_debug_on_exit at /home/zack/emacs/src/eval.c:159
(inlined by) Ffuncall at /home/zack/emacs/src/eval.c:2791
exec_byte_code at /home/zack/emacs/src/bytecode.c:919
funcall_lambda at /home/zack/emacs/src/eval.c:2951
backtrace_debug_on_exit at /home/zack/emacs/src/eval.c:159
(inlined by) Ffuncall at /home/zack/emacs/src/eval.c:2791
exec_byte_code at /home/zack/emacs/src/bytecode.c:919
funcall_lambda at /home/zack/emacs/src/eval.c:2951
backtrace_debug_on_exit at /home/zack/emacs/src/eval.c:159
(inlined by) Ffuncall at /home/zack/emacs/src/eval.c:2791
SPECPDL_INDEX at /home/zack/emacs/src/lisp.h:2998
(inlined by) Ffuncall_interactively at
/home/zack/emacs/src/callint.c:246
Ffuncall at /home/zack/emacs/src/eval.c:2698
Fapply at /home/zack/emacs/src/eval.c:2341
```

Thanks!

-- 
Zack Piper <zack@apertron.net> http://apertron.net



             reply	other threads:[~2015-06-05 10:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 10:20 Zack Piper [this message]
2015-06-05 10:24 ` Random segfaults when using M-x Zack Piper
2015-06-05 13:59   ` Eli Zaretskii
2015-06-05 13:07 ` Stephen Leake
2015-06-05 13:24   ` Przemysław Wojnowski
2015-06-05 14:00   ` Eli Zaretskii
2015-06-08  2:00     ` Stephen Leake
2015-06-05 14:17   ` Eli Zaretskii
2015-06-08  2:01     ` Stephen Leake
2015-06-05 13:25 ` Zack Piper
2015-06-05 13:32   ` Zack Piper
2015-06-05 19:25     ` Eli Zaretskii
2015-06-05 19:29       ` Zack Piper
2015-06-05 13:58 ` Eli Zaretskii

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=20150605102048.GA31678@apertron.net \
    --to=zack@apertron.net \
    --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).