From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/6] [gdb/testsuite] Refactor lock_file_{acquire,release}
Date: Tue, 29 Sep 2026 13:12:57 +0200 [thread overview]
Message-ID: <20260929111257.1910282-1-tdevries@suse.de> (raw)
This series contains some patches that:
- refactor lock_file_{acquire,release}
- add and improve test-case gdb.testsuite/lock.exp
Changes in v2:
- split up patch into 6 patches
- explain better why the loop is minimized
- simplify the on_entry approach by making it a proc name instead of an
uplevel body
- fix pre-existing nit: double space
Versions:
- v1 https://sourceware.org/pipermail/gdb-patches/2026-September/230651.html
Tom de Vries (6):
[gdb/testsuite] Add gdb.testsuite/lock.exp
[gdb/testsuite] Improve variable names in lock_file_{acquire,release}
[gdb/testsuite] Simplify lock_file_acquire
[gdb/testsuite] Only retry on EEXIST in lock_file_acquire
[gdb/testsuite] Extend gdb.testsuite/lock.exp
[gdb/testsuite] Extend gdb.testsuite/lock.exp a bit more
gdb/testsuite/gdb.testsuite/lock.exp | 91 ++++++++++++++++++++++++++++
gdb/testsuite/lib/gdb-utils.exp | 58 +++++++++++-------
2 files changed, 127 insertions(+), 22 deletions(-)
create mode 100644 gdb/testsuite/gdb.testsuite/lock.exp
base-commit: 4ba6bd8393418b63dc3efa0ec6f934903a10f140
--
2.51.0
reply other threads:[~2026-09-29 11:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260929111257.1910282-1-tdevries@suse.de \
--to=tdevries@suse.de \
--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