From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50043@debbugs.gnu.org
Subject: bug#50043: 28.0.50; USABLE_SIGOI undef code paths do not work correctly
Date: Fri, 13 Aug 2021 16:31:52 +0200 [thread overview]
Message-ID: <87mtpla013.fsf@gnus.org> (raw)
In-Reply-To: <835yw9cwoa.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 Aug 2021 16:16:05 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> can you tell where does it hang, and why? Bonus points for explaining
> why the same scenario doesn't hang for USABLE_SIGIO platforms.
It's hanging here:
x_get_foreign_selection (Lisp_Object selection_symbol, Lisp_Object target_type,
Lisp_Object time_stamp, Lisp_Object frame)
{
[...]
wait_reading_process_output (secs, nsecs, 0, false,
reading_selection_reply, NULL, 0);
That is, it's not really hanging hanging, but this sometimes takes a
couple of seconds without SIGIO, while it returns instantaneously with
SIGOI.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-13 14:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 11:56 bug#50043: 28.0.50; USABLE_SIGOI undef code paths do not work correctly Lars Ingebrigtsen
2021-08-13 13:16 ` Eli Zaretskii
2021-08-13 14:31 ` Lars Ingebrigtsen [this message]
2021-08-13 15:51 ` Eli Zaretskii
2021-08-14 11:52 ` Lars Ingebrigtsen
2021-11-15 15:19 ` Ken Brown
2021-11-15 17:24 ` Eli Zaretskii
2021-11-15 19:26 ` Ken Brown
2021-11-16 17:44 ` Eli Zaretskii
2021-11-16 23:06 ` Ken Brown
2021-11-17 7:41 ` Lars Ingebrigtsen
2021-11-17 14:25 ` Ken Brown
2021-11-17 13:14 ` Eli Zaretskii
2021-11-17 14:19 ` Ken Brown
2021-11-17 14:34 ` Eli Zaretskii
2021-11-17 14:59 ` Ken Brown
2021-11-17 16:56 ` Eli Zaretskii
2021-11-17 17:25 ` Ken Brown
2021-11-17 17:37 ` Eli Zaretskii
2021-11-17 17:45 ` Ken Brown
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=87mtpla013.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50043@debbugs.gnu.org \
--cc=eliz@gnu.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 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.