GNU bug report logs - #22136
[osx] core dump while building emacs-25

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22136 in the body.
You can then email your comments to 22136 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Alex Dunn <dunn.alex <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: [osx] core dump while building emacs-25
Date: Wed, 09 Dec 2015 20:20:44 -0800

`make -C ../lisp update-subdirs` on the emacs-25 branch has been
reliably causing a core dump the past two or three days.  Here are the
build logs: https://gist.github.com/dunn/ff087e9b533d373ab10b#file-03-make-L568

It doesn’t cause the build to fail (except for when I made some changes
to the source tree that I can’t reproduce; logs here if anyone’s
interested: https://gist.github.com/dunn/43f10877f11c97ab28f0#file-03-make-L291) so
I don’t know how serious an issue this is.  It occurs with -j1 and -j4,
with Clang and with GCC 5.3.0.

System config included in the logs, but for the sake of convenience:

CPU: quad-core 64-bit haswell
OS X: 10.11.2-x86_64
Xcode: 7.1.1
CLT: 7.2.0.0.1.1447826929

🌲  clang -v
Apple LLVM version 7.0.0 (clang-700.1.76)
Target: x86_64-apple-darwin15.2.0
Thread model: posix

🌲  gcc-5 -v
Using built-in specs.
COLLECT_GCC=gcc-5
COLLECT_LTO_WRAPPER=/usr/local/Cellar/gcc/5.3.0/libexec/gcc/x86_64-apple-darwin15.0.0/5.3.0/lto-wrapper
Target: x86_64-apple-darwin15.0.0
Configured with: ../configure --build=x86_64-apple-darwin15.0.0 --prefix=/usr/local/Cellar/gcc/5.3.0 --libdir=/usr/local/Cellar/gcc/5.3.0/lib/gcc/5 --enable-languages=c,c++,objc,obj-c++,fortran --program-suffix=-5 --with-gmp=/usr/local/opt/gmp --with-mpfr=/usr/local/opt/mpfr --with-mpc=/usr/local/opt/libmpc --with-isl=/usr/local/opt/isl --with-system-zlib --enable-libstdcxx-time=yes --enable-stage1-checking --enable-checking=release --enable-lto --with-build-config=bootstrap-debug --disable-werror --with-pkgversion='Homebrew gcc 5.3.0' --with-bugurl=https://github.com/Homebrew/homebrew/issues --enable-plugin --disable-nls --enable-multilib
Thread model: posix
gcc version 5.3.0 (Homebrew gcc 5.3.0)

If there’s any necessary information I’m forgetting please let me know.

Message #8 received at 22136 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alex Dunn <dunn.alex <at> gmail.com>
Cc: 22136 <at> debbugs.gnu.org
Subject: Re: bug#22136: [osx] core dump while building emacs-25
Date: Thu, 10 Dec 2015 18:19:10 +0200

> From: Alex Dunn <dunn.alex <at> gmail.com>
> Date: Wed, 09 Dec 2015 20:20:44 -0800
> 
> 
> `make -C ../lisp update-subdirs` on the emacs-25 branch has been
> reliably causing a core dump the past two or three days.  Here are the
> build logs: https://gist.github.com/dunn/ff087e9b533d373ab10b#file-03-make-L568
> 
> It doesn’t cause the build to fail (except for when I made some changes
> to the source tree that I can’t reproduce; logs here if anyone’s
> interested: https://gist.github.com/dunn/43f10877f11c97ab28f0#file-03-make-L291) so
> I don’t know how serious an issue this is.  It occurs with -j1 and -j4,
> with Clang and with GCC 5.3.0.

Can you show the core dump itself, i.e. what command dumps core?
Also, a backtrace from GDB would be useful.  I looked at the data you
linked to, and I cannot see there any information about the crash
itself.

Thanks.

Message #11 received at 22136 <at> debbugs.gnu.org (full text, mbox):

From: Alex Dunn <dunn.alex <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 22136 <at> debbugs.gnu.org
Subject: Re: bug#22136: [osx] core dump while building emacs-25
Date: Fri, 11 Dec 2015 23:48:20 -0800

Haven’t forgotten about this, but it’s new territory for me and
apparently capturing core dumps isn’t as straightforward as it should be
on OSX.  Or I’m just confused; but either way I’ll figure it out when I
can.

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Alex Dunn <dunn.alex <at> gmail.com>
>> Date: Wed, 09 Dec 2015 20:20:44 -0800
>> 
>> 
>> `make -C ../lisp update-subdirs` on the emacs-25 branch has been
>> reliably causing a core dump the past two or three days.  Here are the
>> build logs: https://gist.github.com/dunn/ff087e9b533d373ab10b#file-03-make-L568
>> 
>> It doesn’t cause the build to fail (except for when I made some changes
>> to the source tree that I can’t reproduce; logs here if anyone’s
>> interested: https://gist.github.com/dunn/43f10877f11c97ab28f0#file-03-make-L291) so
>> I don’t know how serious an issue this is.  It occurs with -j1 and -j4,
>> with Clang and with GCC 5.3.0.
>
> Can you show the core dump itself, i.e. what command dumps core?
> Also, a backtrace from GDB would be useful.  I looked at the data you
> linked to, and I cannot see there any information about the crash
> itself.
>
> Thanks.

Message #14 received at 22136 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alex Dunn <dunn.alex <at> gmail.com>
Cc: 22136 <at> debbugs.gnu.org
Subject: Re: bug#22136: [osx] core dump while building emacs-25
Date: Sat, 12 Dec 2015 09:58:49 +0200

> From: Alex Dunn <dunn.alex <at> gmail.com>
> Cc: 22136 <at> debbugs.gnu.org
> Date: Fri, 11 Dec 2015 23:48:20 -0800
> 
> Haven’t forgotten about this, but it’s new territory for me and
> apparently capturing core dumps isn’t as straightforward as it should be
> on OSX.  Or I’m just confused; but either way I’ll figure it out when I
> can.

Just run the crashing command under GDB, and when it crashes produce a
backtrace.

Thanks.

Message #17 received at 22136 <at> debbugs.gnu.org (full text, mbox):

From: John Wiegley <jwiegley <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Alex Dunn <dunn.alex <at> gmail.com>, 22136 <at> debbugs.gnu.org
Subject: Re: bug#22136: [osx] core dump while building emacs-25
Date: Mon, 14 Dec 2015 17:56:43 -0800

>>>>> Eli Zaretskii <eliz <at> gnu.org> writes:

> Just run the crashing command under GDB, and when it crashes produce a
> backtrace.

Or, depending on your Xcode version, using lldb. The same commands should
apply.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

Message #20 received at 22136 <at> debbugs.gnu.org (full text, mbox):

From: Alan Third <alan <at> idiocy.org>
To: Alex Dunn <dunn.alex <at> gmail.com>
Cc: 22136 <at> debbugs.gnu.org
Subject: Re: bug#22136: [osx] core dump while building emacs-25
Date: Wed, 18 May 2016 21:19:40 +0100

Alex Dunn <dunn.alex <at> gmail.com> writes:

> Haven’t forgotten about this, but it’s new territory for me and
> apparently capturing core dumps isn’t as straightforward as it should be
> on OSX.  Or I’m just confused; but either way I’ll figure it out when I
> can.

Hi, did you get anywhere with this?
-- 
Alan Third

Message #25 received at 22136 <at> debbugs.gnu.org (full text, mbox):

From: Alex Dunn <dunn.alex <at> gmail.com>
To: Alan Third <alan <at> idiocy.org>
Cc: 22136 <at> debbugs.gnu.org
Subject: Re: bug#22136: [osx] core dump while building emacs-25
Date: Thu, 19 May 2016 06:27:57 -0700

Afraid I didn’t; but I haven’t noticed it occuring on recent builds of
the emacs-25 branch, so it may have been fixed.

Alan Third <alan <at> idiocy.org> writes:

> Alex Dunn <dunn.alex <at> gmail.com> writes:
>
>> Haven’t forgotten about this, but it’s new territory for me and
>> apparently capturing core dumps isn’t as straightforward as it should be
>> on OSX.  Or I’m just confused; but either way I’ll figure it out when I
>> can.
>
> Hi, did you get anywhere with this?
> -- 
> Alan Third

Message #30 received at 22136-done <at> debbugs.gnu.org (full text, mbox):

From: Alan Third <alan <at> idiocy.org>
To: Alex Dunn <dunn.alex <at> gmail.com>
Cc: 22136-done <at> debbugs.gnu.org
Subject: Re: bug#22136: [osx] core dump while building emacs-25
Date: Sat, 21 May 2016 08:38:23 +0100

On Thu, May 19, 2016 at 06:27:57AM -0700, Alex Dunn wrote:
> Afraid I didn’t; but I haven’t noticed it occuring on recent builds of
> the emacs-25 branch, so it may have been fixed.

Since I can't reproduce it, and you don't seem to be getting it any
more I'll mark this bug report as closed. If it does reoccur you can
either then reopen this bug, or create a new one.
-- 
Alan Third

Previous Next

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