unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 55628@debbugs.gnu.org, larsi@gnus.org
Subject: bug#55628: debug-timer-check fails on macOS 11.6.6
Date: Wed, 25 May 2022 17:02:03 +0300	[thread overview]
Message-ID: <83h75d4so4.fsf@gnu.org> (raw)
In-Reply-To: <015331C8-C4AF-49DB-A859-BE01012B77BF@acm.org> (message from Mattias Engdegård on Wed, 25 May 2022 15:05:32 +0200)

> Cc: 55628@debbugs.gnu.org
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Wed, 25 May 2022 15:05:32 +0200
> 
> Thanks for checking. Apparently pending_signals is never set; handle_alarm_signal is never called.
> More digging shows that set_alarm always sets the interval timer to at least 1 ms in the future even if the timer has expired.
> 
> The attached patch makes set_alarm signal SIGALRM immediately if the timer is due. We could call the signal handler directly but this way it should work correctly if the signal is masked at the moment. What do you think?

I'd prefer not to change the logic of set_alarm just to have a
debugging aid working.  Can we come up with a more compatible change,
which doesn't affect calls to set_alarm except during this test?

Thanks.





  reply	other threads:[~2022-05-25 14:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 10:46 bug#55628: debug-timer-check fails on macOS 11.6.6 Mattias Engdegård
2022-05-25 12:20 ` Lars Ingebrigtsen
2022-05-25 13:05   ` Mattias Engdegård
2022-05-25 14:02     ` Eli Zaretskii [this message]
2022-05-25 15:34     ` Mattias Engdegård
2022-05-25 17:11       ` Eli Zaretskii
2022-05-26  9:57         ` Mattias Engdegård
2022-05-26 11:37           ` Eli Zaretskii
2022-05-26 13:15             ` Mattias Engdegård
2022-05-30 10:43               ` Mattias Engdegård
2022-05-30 13:42                 ` Lars Ingebrigtsen
2022-05-30 13:55                   ` Mattias Engdegård

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83h75d4so4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55628@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mattiase@acm.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).