From: Daniel Colascione <dancol@dancol.org>
To: Eric Hanchrow <eric.hanchrow@gmail.com>, 19980@debbugs.gnu.org
Subject: bug#19980: master: `Backtrace after malloc arena is corrupted` causes segfault during build
Date: Sun, 01 Mar 2015 19:38:16 -0800 [thread overview]
Message-ID: <54F3DB28.90402@dancol.org> (raw)
In-Reply-To: <CAHZoxq8tOrLpwBMGYYmYZEks66c_TcEGjCSchRS0ONRMQFM4+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On 03/01/2015 07:28 PM, Eric Hanchrow wrote:
> Program received signal SIGSEGV, Segmentation fault.
> __GI___backtrace (array=array@entry=0xbfffedcc, size=size@entry=0) at
> ../sysdeps/i386/backtrace.c:141
> 141../sysdeps/i386/backtrace.c: No such file or directory.
> (gdb) bt
> #0 __GI___backtrace (array=array@entry=0xbfffedcc, size=size@entry=0)
> at ../sysdeps/i386/backtrace.c:141
> #1 0x080ed543 in emacs_backtrace
> (backtrace_limit=backtrace_limit@entry=-1) at sysdep.c:2177
> #2 0x0804f744 in main (argc=<optimized out>, argv=0xbffff6d4) at
> emacs.c:887
> (gdb)
So we're crashing inside glibc's backtrace? Between this crash and the
bug that commit b74db6347cf5cac1ebd4c604fd5691c588fd8e32 is trying to
work around, maybe we should link against libunwind instead of using the
system backtrace.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-02 3:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 16:39 Segfault in master David Kastrup
2015-03-05 4:39 ` Paul Eggert
2015-03-05 9:31 ` Colin Baxter
2015-03-05 20:01 ` bug#19959: " Paul Eggert
2015-03-05 20:01 ` Paul Eggert
2015-03-02 3:28 ` bug#19980: master: `Backtrace after malloc arena is corrupted` causes segfault during build Eric Hanchrow
2015-03-02 3:38 ` Daniel Colascione [this message]
[not found] ` <handler.19980.D19959.142558572217560.notifdone@debbugs.gnu.org>
2015-03-05 21:20 ` bug#19980: closed (Re: Segfault in master) Eric Hanchrow
2015-03-05 16:19 ` Segfault in master Thomas Fitzsimmons
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=54F3DB28.90402@dancol.org \
--to=dancol@dancol.org \
--cc=19980@debbugs.gnu.org \
--cc=eric.hanchrow@gmail.com \
/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.