From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [RFC 0/3] [gdb/dap] Fix issues triggered by gdb.dap/eof.exp
Date: Wed, 7 Feb 2024 10:02:21 +0100 [thread overview]
Message-ID: <20240207090224.27521-1-tdevries@suse.de> (raw)
When running test-case gdb.dap/eof.exp on aarch64-linux, sometimes I run into
a gdb segfault.
This series makes the test-case pass reliably.
The series consists of three patches.
The second one seems obvious to me, and doesn't depend on the other patches.
The first and last I'm not sure about, so this series is an RFC.
Tested on aarch64-linux.
Tested by running the dap test-cases 500 times in a row.
Tom de Vries (3):
[gdb/dap] Fix exit race
[gdb/dap] Catch and log exceptions in dap threads
[gdb/dap] Ignore OSError on stream.flush in JSON writer
gdb/python/lib/gdb/dap/io.py | 6 ++++--
gdb/python/lib/gdb/dap/startup.py | 20 ++++++++++++++++++--
2 files changed, 22 insertions(+), 4 deletions(-)
base-commit: 0afc614c9938fbf5eda10a26c77d574c3c2f945a
--
2.35.3
next reply other threads:[~2024-02-07 9:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 9:02 Tom de Vries [this message]
2024-02-07 9:02 ` [RFC 1/3] [gdb/dap] Fix exit race Tom de Vries
2024-02-07 16:01 ` Tom Tromey
2024-02-13 15:04 ` Tom de Vries
2024-02-13 18:04 ` Tom Tromey
2024-02-13 18:11 ` Tom Tromey
2024-02-14 15:31 ` Tom de Vries
2024-02-14 15:34 ` Tom Tromey
2024-02-14 15:53 ` Tom de Vries
2024-02-14 16:18 ` Tom Tromey
2024-02-14 17:16 ` Tom de Vries
2024-02-07 9:02 ` [RFC 2/3] [gdb/dap] Catch and log exceptions in dap threads Tom de Vries
2024-02-07 15:52 ` Tom Tromey
2024-02-12 15:15 ` Tom de Vries
2024-02-12 17:35 ` Tom Tromey
2024-02-07 9:02 ` [RFC 3/3] [gdb/dap] Ignore OSError on stream.flush in JSON writer Tom de Vries
2024-02-07 10:29 ` Tom de Vries
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=20240207090224.27521-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).