From: Eli Zaretskii <eliz@gnu.org>
To: zack@apertron.net
Cc: 20748@debbugs.gnu.org
Subject: bug#20748: 25.0.50; Seemingly random segfaults.
Date: Sat, 06 Jun 2015 10:43:47 +0300 [thread overview]
Message-ID: <83bngtnux8.fsf@gnu.org> (raw)
In-Reply-To: <ma1thqc4s0.fsf@xieshaij.i-did-not-set--mail-host-address--so-tickle-me>
> From: zack@apertron.net
> Date: Fri, 05 Jun 2015 19:51:43 +0000
>
> Starting program: /home/zack/ins/bin/emacs
> Got object file from memory but can't read symbols: File truncated.
A strange message, don't you think?
> Program received signal SIGSEGV, Segmentation fault.
> turn_on_face (f=f@entry=0xcde8f8, face_id=face_id@entry=74) at term.c:1902
> 1902 unsigned long fg = face->foreground;
> #0 0x00000000004dc28a in turn_on_face (f=f@entry=0xcde8f8, face_id=face_id@entry=74) at term.c:1902
> face = 0x0
Please show the output of these GDB commands:
(gdb) frame 0
(gdb) p f->face_cache->used
The first command assumes that "frame 0" is the one shown above, a
call to turn_on_face. The frame number is that #0 part at the left
edge of the line. If the next time it happens you will see the call
to turn_on_face in a different stack frame, use that frame's number
instead of zero in the first command above.
Did you build this Emacs yourself? If so, can you also build a
non-optimized version, and see if the problem happens there? To build
a non-optimized Emacs, configure it like this:
CFLAGS='-O0 -g3' ./configure --enable-checking='yes,glyphs' ...
Replace "..." with the rest of your configure-time options.
Finally, do you have a lot of customizations in your ~/.emacs? I'm
puzzled by the large number of the face ID (74) in the backtrace -- do
you customize your faces a lot, or use packages that create a lot of
faces?
Thanks.
next prev parent reply other threads:[~2015-06-06 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 19:51 bug#20748: 25.0.50; Seemingly random segfaults zack
2015-06-06 7:43 ` Eli Zaretskii [this message]
2015-06-06 9:54 ` Zack Piper
2015-06-06 19:09 ` Eli Zaretskii
2017-11-29 2:05 ` Noam Postavsky
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=83bngtnux8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20748@debbugs.gnu.org \
--cc=zack@apertron.net \
/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).