all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 75275@debbugs.gnu.org, Alan Third <alan@idiocy.org>
Subject: bug#75275: 30.0.92; `make-thread` bug on macOS 15.2
Date: Thu, 02 Jan 2025 15:45:16 +0100	[thread overview]
Message-ID: <m2ttahgtqb.fsf@gmail.com> (raw)
In-Reply-To: <m2y0ztgu0z.fsf@gmail.com> ("Gerd Möllmann"'s message of "Thu, 02 Jan 2025 15:38:52 +0100")

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Thanks, I didn't have time to look into the above yet, but I noticed
>> that the bug wasn't there on emacs-29 and bisected the issue:
>>
>> 4ac4cec652ffaca4333d8f297b8a6c0e5bd79c68 is the first bad commit
>> commit 4ac4cec652ffaca4333d8f297b8a6c0e5bd79c68
>> Author: Gerd Möllmann <gerd@gnu.org>
>> Date:   Sat Mar 9 15:06:29 2024 +0100
>>
>>     Prevent freezes on macOS (bug#69561)
>
> Thanks, there he is, the culprit :-).
>
> I don't know what to do now.

Maybe this one, after what Alan explained. Could you try it?

1 file changed, 2 insertions(+), 2 deletions(-)
src/nsterm.m | 4 ++--

modified   src/nsterm.m
@@ -4875,8 +4875,8 @@ Function modeled after x_draw_glyph_string_box ().
 
   if (![NSThread isMainThread]
       || (timeout && timeout->tv_sec == 0 && timeout->tv_nsec == 0))
-    thread_select (pselect, nfds, readfds, writefds,
-		   exceptfds, timeout, sigmask);
+    return thread_select (pselect, nfds, readfds, writefds,
+			  exceptfds, timeout, sigmask);
   else
     {
       struct timespec t = {0, 0};






  reply	other threads:[~2025-01-02 14:45 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02  4:57 bug#75275: 30.0.92; `make-thread` bug on macOS 15.2 Stefan Kangas
2025-01-02  5:46 ` Gerd Möllmann
2025-01-02  5:55   ` Gerd Möllmann
2025-01-02  6:47   ` Stefan Kangas
2025-01-02  7:12     ` Gerd Möllmann
2025-01-02 14:35       ` Stefan Kangas
2025-01-02 14:38         ` Gerd Möllmann
2025-01-02 14:45           ` Gerd Möllmann [this message]
2025-01-02 15:19             ` Stefan Kangas
2025-01-02 16:06               ` Alan Third
2025-01-02 16:47                 ` Alan Third
2025-01-02 16:58                 ` Eli Zaretskii
2025-01-02 17:09                   ` Gerd Möllmann
2025-01-02 17:22                     ` Eli Zaretskii
2025-01-02 17:25                       ` Gerd Möllmann
2025-01-02 17:42                         ` Alan Third
2025-01-02 17:48                           ` Gerd Möllmann
2025-01-02 17:37                       ` Alan Third
2025-01-02 17:46                         ` Gerd Möllmann
2025-01-02 17:52                           ` Gerd Möllmann
2025-01-02 19:26                             ` Alan Third
2025-01-02 19:59                               ` Gerd Möllmann
2025-01-02 16:46               ` Eli Zaretskii
2025-01-02  7:53     ` Eli Zaretskii
2025-01-02  7:58       ` Stefan Kangas
2025-01-02  7:13 ` Eli Zaretskii
2025-01-02  7:30   ` Gerd Möllmann
2025-01-02  8:28     ` Eli Zaretskii
2025-01-02  8:33       ` Gerd Möllmann
2025-01-02  8:41         ` Gerd Möllmann
2025-01-02  8:55           ` Eli Zaretskii
2025-01-02 10:04             ` Gerd Möllmann
2025-01-02 11:03               ` Alan Third
2025-01-02 13:05                 ` Gerd Möllmann
2025-01-02 13:53                   ` Alan Third
2025-01-02 14:03                     ` Gerd Möllmann
2025-01-02 14:17                       ` Alan Third
2025-01-02 15:31                 ` Eli Zaretskii
2025-01-02 15:37                   ` Gerd Möllmann
2025-01-02 15:55                     ` Alan Third
2025-01-02 16:08                       ` Gerd Möllmann
2025-01-02  8:51         ` Gerd Möllmann
2025-01-02  7:31   ` Stefan Kangas
2025-01-02  8:31     ` Eli Zaretskii
2025-01-02 10:31     ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=m2ttahgtqb.fsf@gmail.com \
    --to=gerd.moellmann@gmail.com \
    --cc=75275@debbugs.gnu.org \
    --cc=alan@idiocy.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.