From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: help debugging a segfault
Date: Tue, 18 Oct 2016 08:45:19 +0300 [thread overview]
Message-ID: <83k2d6xlao.fsf@gnu.org> (raw)
In-Reply-To: <ec319455-840a-4b75-82f6-73fbb5115224@googlegroups.com> (message from Sam Halliday on Mon, 17 Oct 2016 13:16:33 -0700 (PDT))
> Date: Mon, 17 Oct 2016 13:16:33 -0700 (PDT)
> From: Sam Halliday <sam.halliday@gmail.com>
>
> Despite being very stable since I installed it when released, Emacs 25.1 has started to segfault on me this week in a hard-to-reproduce manner.
>
> I use ArchLinux and I recompiled with debugging symbols to obtain a detailed core dump / crash log.
>
> But this is all I got when running with gdb until it crashed:
>
> =============================
> 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);
> =============================
Sounds like another case of bug#24358, see
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24358#41
and the following discussion. Your OS is also the same as reported
there, which increases the probability of this being the same issue.
If you ever succeed in getting meaningful data about the crash, or
some way of reproducing it, please post to 24358@debbugs.gnu.org.
prev parent reply other threads:[~2016-10-18 5:45 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k2d6xlao.fsf@gnu.org \
--to=eliz@gnu.org \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.