GNU bug report logs - #66098
Crash in itree.c on macOS with incomplete backtrace

Previous Next

Full log

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

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 66098 <at> debbugs.gnu.org, rpluim <at> gmail.com, acorallo <at> gnu.org
Subject: Re: bug#66098: Crash in itree.c on macOS with incomplete backtrace
Date: Sun, 24 Sep 2023 05:25:38 -0700

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

> Looks like infinite recursion of some sorts?  The function at
> 0x7fb2d9463cb3 calls itself again and again.

Yes, it looks like it.

> Are you saying that the problem doesn't happen without
> native-compilation?

I thought that for a second, but that can't be right since I did see a
crash also without it, in the original bug report:

Configured using:
 'configure --enable-checking=yes,glyphs --enable-check-lisp-object-type
 'CFLAGS=-O0 -g3''

Assuming that was the same crash, of course.

I'm still trying various configurations to find out more, but it's slow
going since I can't seem to find a way to reproduce it consistently.
I'm now running this build:

Configured using:
 'configure 'CFLAGS=-O0 -g3 -fsanitize=address'
 --with-native-compilation CPPFLAGS=-I/usr/local/opt/llvm/include
 LDFLAGS=-L/usr/local/opt/llvm/lib'

Since I did not see this a few weeks ago, perhaps it's time to bite the
bullet and bisect.

Previous Next

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