From: Sam Halliday <sam.halliday@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: help debugging a segfault
Date: Mon, 17 Oct 2016 13:28:01 -0700 (PDT) [thread overview]
Message-ID: <f53409af-c931-4eda-b49f-4ee3e36b7e18@googlegroups.com> (raw)
In-Reply-To: <ec319455-840a-4b75-82f6-73fbb5115224@googlegroups.com>
On Monday, 17 October 2016 21:16:35 UTC+1, Sam Halliday wrote:
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> re_search_2 (bufp=bufp@entry=0xc2d460 <searchbufs+2912>, str1=str1@entry=0x597b790 <error: Cannot access memory at address 0x597b790>, size1=size1@entry=0,
> str2=str2@entry=0x597b790 <error: Cannot access memory at address 0x597b790>, size2=65565, startpos=646, startpos@entry=623, range=509,
> regs=0xc2c8d0 <search_regs>, stop=1155) at regex.c:4464
> 4464 int len = BYTES_BY_CHAR_HEAD (*p);
...
> Could anybody please shed some light on what could be going wrong? I also have a core dump file but I have no idea what to do with it, I've never used gdb in anger.
Typing "bt" when loading the coredump gives
(gdb) bt
#0 0x00007fe8cbfabf5f in ?? ()
#1 0x00000000005da106 in mapcar1 (leni=11, vals=<optimized out>, fn=40, seq=498) at fns.c:2494
#2 0xffffffffffffffff in ?? ()
#3 0xffffffffffffffff in ?? ()
#4 0xffffffffffffffff in ?? ()
#5 0xffffffffffffffff in ?? ()
#6 0xffffffffffffffff in ?? ()
#7 0xffffffffffffffff in ?? ()
#8 0xffffffffffffffff in ?? ()
#9 0x000000000000000b in ?? ()
#10 0x00000000004ee994 in Finternal_merge_in_global_face (face=2, frame=12113136) at xfaces.c:3669
#11 0x0000000000000000 in ?? ()
next prev parent reply other threads:[~2016-10-17 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 20:16 help debugging a segfault Sam Halliday
2016-10-17 20:28 ` Sam Halliday [this message]
2016-10-18 5:48 ` Eli Zaretskii
2016-10-18 7:35 ` Sam Halliday
2016-10-18 9:12 ` Eli Zaretskii
2016-10-17 21:17 ` Óscar Fuentes
2016-10-18 5:45 ` 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=f53409af-c931-4eda-b49f-4ee3e36b7e18@googlegroups.com \
--to=sam.halliday@gmail.com \
--cc=help-gnu-emacs@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.
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).