GNU bug report logs - #75275
30.0.92; `make-thread` bug on macOS 15.2

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: 75275 <at> debbugs.gnu.org, alan <at> idiocy.org, stefankangas <at> gmail.com
Subject: bug#75275: 30.0.92; `make-thread` bug on macOS 15.2
Date: Thu, 02 Jan 2025 10:55:32 +0200

> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
> Cc: stefankangas <at> gmail.com,  alan <at> idiocy.org,  75275 <at> debbugs.gnu.org
> Date: Thu, 02 Jan 2025 09:41:38 +0100
> 
> Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:
> 
> > Eli Zaretskii <eliz <at> gnu.org> writes:
> >
> >> So should we add a condition before calling [NSApp run] that we are in
> >> the main thread?
> >
> > ATM, I don't understand how we land in that line in ns_select_1 if not
> > [NSThread isMainThread]. Maybe I need new glasses. I asked Stefan if he
> > can see something in LLDB.
> 
> It must something in here:
> 
>   if (![NSThread isMainThread]
>       || (timeout && timeout->tv_sec == 0 && timeout->tv_nsec == 0))
>     thread_select (pselect, nfds, readfds, writefds,
> 		   exceptfds, timeout, sigmask);
> 
> Should we return here?

I don't know.  Is there anything in the following code that can be
relevant to a non-main thread?  Note that non-main threads can
legitimately call wait_reading_process_output, which calls ns_select.
For example, what happens if a non-main Lisp thread starts a
sub-process? we do expect to be able to read the output from that
sub-process.

Previous Next

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