GNU bug report logs - #19980
master: `Backtrace after malloc arena is corrupted` causes segfault during build

Previous Next

Package: emacs;

Reported by: Eric Hanchrow <eric.hanchrow <at> gmail.com>

Date: Mon, 2 Mar 2015 03:30:02 UTC

Severity: normal

Merged with 19959, 19974

Found in version 25.0.50

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Daniel Colascione <dancol <at> dancol.org>
To: Eric Hanchrow <eric.hanchrow <at> gmail.com>, 19980 <at> 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

[Message part 1 (text/plain, inline)]
On 03/01/2015 07:28 PM, Eric Hanchrow wrote:
> Program received signal SIGSEGV, Segmentation fault.
> __GI___backtrace (array=array <at> entry=0xbfffedcc, size=size <at> 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 <at> entry=0xbfffedcc, size=size <at> entry=0)
> at ../sysdeps/i386/backtrace.c:141
> #1  0x080ed543 in emacs_backtrace
> (backtrace_limit=backtrace_limit <at> 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.


[signature.asc (application/pgp-signature, attachment)]
This bug report was last modified 10 years and 81 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.