From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Nicolas Richard <theonewiththeevillook@yahoo.fr>, 19959@debbugs.gnu.org
Subject: bug#19959: 25.0.50; can't bootstrap -- temacs dumps core
Date: Tue, 03 Mar 2015 11:23:28 -0500 [thread overview]
Message-ID: <m3zj7udp8f.fsf@fitzsim.org> (raw)
In-Reply-To: <p2zj7zmdb3.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 27 Feb 2015 13:14:56 -0500")
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
Glenn Morris <rgm@gnu.org> writes:
> Nicolas Richard wrote:
>
>> In GNU Emacs 25.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
>
> FWIW, http://hydra.nixos.org/build/19982110 flagged this yesterday.
> It seems to be specific to 32-bit builds.
> (The precise introduction is masked by the previous total build failure
> due to a typo.)
This commit breaks bootstrap for me:
commit b74db6347cf5cac1ebd4c604fd5691c588fd8e32
Author: Paul Eggert <eggert@cs.ucla.edu>
Date: Tue Feb 24 16:34:13 2015 -0800
Backtrace after malloc arena is corrupted
Without this change, if the malloc arena is corrupted and then
'backtrace' is called, the backtrace can crash because 'backtrace'
calls 'malloc'. For more, please see:
https://sourceware.org/ml/libc-alpha/2015-02/msg00678.html
* emacs.c (main): Initialize tables used by 'backtrace'.
* sysdep.c (emacs_backtrace): Document the newly used part of the API.
On my system's glibc version, glibc-2.16-30.fc18.i686, it seems that a
zero size argument to backtrace causes a segfault; minimal example
attached:
$ gcc -Wall backtrace.c
$ env -i ./a.out
Segmentation fault (core dumped)
Thomas
[-- Attachment #2: backtrace.c --]
[-- Type: text/plain, Size: 155 bytes --]
#include <execinfo.h>
int main()
{
void *main_backtrace_buffer[501];
void *buffer;
buffer = main_backtrace_buffer;
return backtrace(buffer, 0);
}
prev parent reply other threads:[~2015-03-03 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 14:51 bug#19959: 25.0.50; can't bootstrap -- temacs dumps core Nicolas Richard
2015-02-27 18:14 ` Glenn Morris
2015-03-03 16:23 ` Thomas Fitzsimmons [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=m3zj7udp8f.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=19959@debbugs.gnu.org \
--cc=rgm@gnu.org \
--cc=theonewiththeevillook@yahoo.fr \
/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.