From: Robert Pluim <rpluim@gmail.com>
To: Pip Cet <pipcet@gmail.com>
Cc: alan@idiocy.org, jguenther@gmail.com,
Andrii Kolomoiets <andreyk.mad@gmail.com>,
38748@debbugs.gnu.org
Subject: bug#38748: 28.0.50; crash on MacOS 10.15.2
Date: Wed, 08 Jan 2020 23:23:48 +0100 [thread overview]
Message-ID: <m2r209si2z.fsf@gmail.com> (raw)
In-Reply-To: <CAOqdjBeLC9Y99eiGJ8D9wgKxZo73kHozOQaRiZsJcuOr=cT5xA@mail.gmail.com> (Pip Cet's message of "Wed, 8 Jan 2020 22:18:11 +0000")
>>>>> On Wed, 8 Jan 2020 22:18:11 +0000, Pip Cet <pipcet@gmail.com> said:
Pip> On Wed, Jan 8, 2020 at 9:43 PM Robert Pluim <rpluim@gmail.com> wrote:
>> gcc --version
>> Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
>> Apple LLVM version 10.0.1 (clang-1001.0.46.4)
>> Target: x86_64-apple-darwin18.7.0
>> Thread model: posix
>> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
>>
>> Iʼve attached the disassembly of the two versions. They're very very
>> similar (this is with -g3 -O0).
Pip> But wait, doesn't the bug happen in both unoptimized versions? I
Pip> should have been clearer: my suspicion is the bug only goes away if
Pip> tail calls are optimized, which happens only with optimizations
Pip> enabled.
No, it only happens with the initialisation of 'ok', optimised or not.
As another data point, Iʼm writing this from an emacs with 'ok =
true', which has not crashed yet....
Robert
next prev parent reply other threads:[~2020-01-08 22:23 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 9:47 bug#38748: 28.0.50; crash on MacOS 10.15.2 Andrii Kolomoiets
2019-12-26 13:04 ` Alan Third
2019-12-26 17:18 ` Eli Zaretskii
2019-12-27 11:28 ` Andrii Kolomoiets
2019-12-27 14:14 ` Eli Zaretskii
2019-12-29 19:01 ` Andrii Kolomoiets
2019-12-29 19:31 ` Eli Zaretskii
2020-01-01 20:42 ` Andrii Kolomoiets
2020-01-02 14:06 ` Eli Zaretskii
2020-01-08 17:39 ` Robert Pluim
2020-01-08 19:18 ` Pip Cet
2020-01-08 19:58 ` Eli Zaretskii
2020-01-08 20:39 ` Pip Cet
2020-01-09 3:30 ` Eli Zaretskii
2020-01-10 7:32 ` Pip Cet
2020-01-10 8:27 ` Eli Zaretskii
2020-01-10 8:58 ` Robert Pluim
2020-01-10 9:21 ` Eli Zaretskii
2020-01-10 10:18 ` Robert Pluim
2020-01-11 6:26 ` Pankaj Jangid
2020-01-11 8:08 ` Eli Zaretskii
2020-01-11 10:43 ` Pankaj Jangid
2020-01-11 12:14 ` Eli Zaretskii
2020-01-10 9:22 ` Pip Cet
2020-01-10 9:33 ` Eli Zaretskii
2020-01-11 13:59 ` Alan Third
2020-01-11 14:13 ` Pip Cet
2020-01-11 19:07 ` Alan Third
2020-01-08 21:43 ` Robert Pluim
2020-01-08 22:18 ` Pip Cet
2020-01-08 22:23 ` Robert Pluim [this message]
2020-01-09 7:51 ` Robert Pluim
2020-01-09 10:07 ` Eli Zaretskii
2020-01-09 10:31 ` Robert Pluim
2020-01-09 14:10 ` Pip Cet
2020-01-09 14:16 ` Eli Zaretskii
2020-01-09 14:56 ` Robert Pluim
2020-01-09 17:06 ` Eli Zaretskii
2020-01-09 13:51 ` Andrii Kolomoiets
2020-01-09 14:13 ` Robert Pluim
2020-01-09 14:16 ` Pip Cet
2020-01-09 14:29 ` Andrii Kolomoiets
2020-01-09 15:15 ` Robert Pluim
2020-01-11 18:37 ` Pieter van Oostrum
2020-01-11 18:43 ` Eli Zaretskii
2020-01-11 21:23 ` Pieter van Oostrum
2020-01-12 3:33 ` Eli Zaretskii
2020-01-11 19:14 ` Pip Cet
2020-01-11 21:36 ` Pieter van Oostrum
2020-01-04 16:48 ` Pieter van Oostrum
2020-01-04 17:25 ` Alan Third
2020-01-05 19:41 ` Pieter van Oostrum
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=m2r209si2z.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=38748@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=andreyk.mad@gmail.com \
--cc=jguenther@gmail.com \
--cc=pipcet@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.