From: Alex Dunn <dunn.alex@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22136@debbugs.gnu.org
Subject: bug#22136: [osx] core dump while building emacs-25
Date: Fri, 11 Dec 2015 23:48:20 -0800 [thread overview]
Message-ID: <m2poycgla3.fsf@snow.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <83zixi9szl.fsf@gnu.org>
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@gnu.org> writes:
>> From: Alex Dunn <dunn.alex@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.
next prev parent reply other threads:[~2015-12-12 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 4:20 bug#22136: [osx] core dump while building emacs-25 Alex Dunn
2015-12-10 16:19 ` Eli Zaretskii
2015-12-12 7:48 ` Alex Dunn [this message]
2015-12-12 7:58 ` Eli Zaretskii
2015-12-15 1:56 ` John Wiegley
2016-05-18 20:19 ` Alan Third
2016-05-19 13:27 ` Alex Dunn
2016-05-21 7:38 ` Alan Third
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=m2poycgla3.fsf@snow.i-did-not-set--mail-host-address--so-tickle-me \
--to=dunn.alex@gmail.com \
--cc=22136@debbugs.gnu.org \
--cc=eliz@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.