From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 48629@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#48629: 28.0.50; GUI emacsclient frames stop accepting keyboard input around recv
Date: Wed, 26 May 2021 19:10:30 +0100 [thread overview]
Message-ID: <87a6ohpdrd.fsf@tcd.ie> (raw)
In-Reply-To: <83h7ip9zne.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 May 2021 20:24:21 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 48629@debbugs.gnu.org
>> Date: Wed, 26 May 2021 16:58:17 +0100
>>
>> Thread 1 (Thread 0x7fb2f78e9040 (LWP 46955) "emacs"):
>> #0 0x00007fb2fa7ae9c6 in __pselect (nfds=24, readfds=0x7ffc492342e0,
>> writefds=0x7ffc49234360, exceptfds=0x0, timeout=<optimized out>,
>> sigmask=0x7ffc49234130) at ../sysdeps/unix/sysv/linux/pselect.c:48
>> resultvar = 18446744073709551102
>> sc_cancel_oldtype = 0
>> tval = {tv_sec = 14, tv_nsec = 461936780}
>> data = {ss = 0, ss_len = 8}
>> #1 0x000055dfc63615b6 in really_call_select ()
>> #2 0x000055dfc6362320 in thread_select ()
>> #3 0x000055dfc637ef58 in xg_select ()
>> #4 0x000055dfc633f89d in wait_reading_process_output ()
>> #5 0x000055dfc62843e8 in read_char ()
>> #6 0x000055dfc6286822 in read_key_sequence ()
>> #7 0x000055dfc628822c in command_loop_1 ()
>
> This is slightly more interesting, because it shows that timeout for
> pselect was 14 sec plus change. So the interesting question is what
> happens after the timeout expires?
>
> IOW, when you find Emacs stuck in pselect, type "finish" and let Emacs
> exit the pselect call.
I did this, and it returned zero after a while:
Attaching to process 46955
[New LWP 46956]
[New LWP 46957]
[New LWP 46958]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fb2fa7ae9c6 in __pselect (nfds=24, readfds=0x7ffc492342e0, writefds=0x7ffc49234360, exceptfds=0x0,
timeout=<optimized out>, sigmask=0x7ffc49234130) at ../sysdeps/unix/sysv/linux/pselect.c:48
48 ../sysdeps/unix/sysv/linux/pselect.c: No such file or directory.
(gdb) finish
Run till exit from #0 0x00007fb2fa7ae9c6 in __pselect (nfds=24, readfds=0x7ffc492342e0, writefds=0x7ffc49234360,
exceptfds=0x0, timeout=<optimized out>, sigmask=0x7ffc49234130) at ../sysdeps/unix/sysv/linux/pselect.c:48
0x000055dfc63615b6 in really_call_select ()
Value returned is $1 = 0
> Then step through the code and see what it does and why it doesn't
> respond to keyboard input.
I guess I need debugging symbols for this, because at this point
step/next progressively and slowly climb frames, without any indication
of the surrounding code or values (GDB maintains that it's in pselect.c
the whole time).
> Is the keyboard descriptor in the set of descriptors pselect waits
> for?
How do I determine what the keyboard descriptor is?
Thanks,
--
Basil
next prev parent reply other threads:[~2021-05-26 18:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 16:14 bug#48629: 28.0.50; GUI emacsclient frames stop accepting keyboard input around recv Basil L. Contovounesios
2021-05-24 16:36 ` Eli Zaretskii
2021-05-24 16:56 ` Basil L. Contovounesios
2021-05-24 16:59 ` Eli Zaretskii
2021-05-24 17:12 ` Basil L. Contovounesios
2021-05-24 17:45 ` Andreas Schwab
2021-05-24 18:38 ` Basil L. Contovounesios
2021-05-24 19:00 ` Andreas Schwab
2021-05-26 15:25 ` Basil L. Contovounesios
2021-05-26 15:58 ` Basil L. Contovounesios
2021-05-26 17:24 ` Eli Zaretskii
2021-05-26 18:10 ` Basil L. Contovounesios [this message]
2021-05-26 18:59 ` Eli Zaretskii
2021-06-03 13:18 ` Basil L. Contovounesios
2021-05-26 17:21 ` Eli Zaretskii
2022-07-15 10:24 ` Lars Ingebrigtsen
2022-07-24 3:54 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-24 9:25 ` Lars Ingebrigtsen
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=87a6ohpdrd.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=48629@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@linux-m68k.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).