From: kurku <sandovin@mail.ru>
To: gdb-patches@sourceware.org
Cc: kurku <sandovin@mail.ru>
Subject: [RFC][PATCH 0/2][PR cli/34409] Fix SIGTTIN due to readline macroinput.
Date: Wed, 22 Jul 2026 10:21:35 +0300 [thread overview]
Message-ID: <20260722072137.1397888-1-sandovin@mail.ru> (raw)
The two patches fix (gdb:cli/34409): [gdb receives SIGTTIN when user uses readline macros]
It adds support of any kind of readline macros: the one defined by the user in his ~/.inputrc
or the one, for example, recorded at a debug scene with Cx-( ... Cx-) Cx-e -- into gdb.
[2] I managed to do so by a slight extension of the current event-loop over file
descriptors. Now, apart from direct events like the ones from poll api,
file descriptors also can specify that they have a `synthetic input`
pending associated with them.
[1] It was easy to integrate this new behavior into select round robin, but not poll.
So I reworked the poll's round robin so that it looks like select's version now.
I ran the test-suite via `make check -j$(nproc)` on x86-64 Linux under `guix shell -D gdb clang-toolchain`.
There were unexpected failures fluctuating around 456 in gdb, but no visible regressions between
the original master and my patches on top of it.
I have not previously completed any FSF copyright assignment
This is my first contribution to the project.
kurku (2):
gdb: event-loop: Rework poll's version of round robin
gdb: Fix readline macros hazards.
gdb/event-top.c | 35 +++++++++++
gdb/ui.h | 3 +
gdbsupport/event-loop.cc | 131 +++++++++++++++++++++++++++++----------
gdbsupport/event-loop.h | 4 ++
4 files changed, 139 insertions(+), 34 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-22 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 7:21 kurku [this message]
2026-07-22 7:21 ` [RFC][PATCH 1/2][PR cli/34409] gdb: event-loop: Rework poll's version of round robin kurku
2026-07-22 7:21 ` [RFC][PATCH 2/2][PR cli/34409] gdb: Fix readline macros hazards kurku
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=20260722072137.1397888-1-sandovin@mail.ru \
--to=sandovin@mail.ru \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox