From: Robert Pluim <rpluim@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 66098@debbugs.gnu.org
Subject: bug#66098: Crash in itree.c on macOS with incomplete backtrace
Date: Fri, 22 Sep 2023 14:07:02 +0200 [thread overview]
Message-ID: <871qeqtnrt.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkm=MVmz524RkC=nhj1EzKptDW+PHtp1kF3NZOqxFpV9RhQ@mail.gmail.com> (Stefan Kangas's message of "Fri, 22 Sep 2023 03:58:13 -0700")
>>>>> On Fri, 22 Sep 2023 03:58:13 -0700, Stefan Kangas <stefankangas@gmail.com> said:
>> Iʼd start by adding '-fsanitize=address' to your CFLAGS.
Stefan> I tried that, and the crash disappeared. Nothing has come up so far,
Stefan> not even the bug that you found.
Paul installed a fix on master.
Stefan> However, I had to install a new version of llvm to get asan support, and
Stefan> it seems the new build is using my old clang but CPPFLAGS and LDFLAGS is
Stefan> pointing to the new version. Perhaps that has something to do with it,
Stefan> so I'll try rebuilding without that next.
If you installed using homebrew, then the new clang wonʼt be in $PATH,
since clang is a system binary, so you need to either adjust your
$PATH or pass CC=/path/to/clang to configure.
Robert
--
next prev parent reply other threads:[~2023-09-22 12:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 8:47 bug#66098: Crash in itree.c on macOS with incomplete backtrace Stefan Kangas
2023-09-19 9:23 ` Robert Pluim
2023-09-19 10:09 ` Robert Pluim
2023-09-20 8:08 ` Paul Eggert
2023-09-20 8:22 ` Robert Pluim
2023-09-22 10:58 ` Stefan Kangas
2023-09-22 12:07 ` Robert Pluim [this message]
2023-09-23 13:02 ` Stefan Kangas
2023-09-25 8:36 ` Robert Pluim
2023-09-19 11:24 ` Eli Zaretskii
2023-09-22 10:51 ` Stefan Kangas
2023-09-22 12:36 ` Eli Zaretskii
2023-09-22 12:46 ` Robert Pluim
2023-09-23 11:56 ` Stefan Kangas
2023-09-23 12:42 ` Eli Zaretskii
2023-09-24 10:55 ` Stefan Kangas
2023-09-24 12:10 ` Eli Zaretskii
2023-09-24 12:25 ` Stefan Kangas
2023-09-24 21:01 ` Stefan Kangas
2023-09-25 3:38 ` Gerd Möllmann
2023-09-19 11:42 ` Gerd Möllmann
2023-09-19 12:21 ` Gerd Möllmann
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=871qeqtnrt.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=66098@debbugs.gnu.org \
--cc=stefankangas@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.