From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC 2/3] [gdb/dap] Catch and log exceptions in dap threads
Date: Wed, 07 Feb 2024 08:52:04 -0700 [thread overview]
Message-ID: <87a5occlwb.fsf@tromey.com> (raw)
In-Reply-To: <20240207090224.27521-3-tdevries@suse.de> (Tom de Vries's message of "Wed, 7 Feb 2024 10:02:23 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Thanks for the patch.
Tom> - the DAP thread samples the gdb_stderr value, and uses it a bit later to
Tom> print to
Tom> - the gdb main thread changes the gdb_stderr value forth and back,
Tom> using a temporary value for string capture purposes
I think the first bullet point here is incomplete.
Tom> + # Catch any exception, and log it. If we let it escape here, it
Tom> + # it'll be printed in gdb_stderr, which is not safe to access from
Remove the "it" at the end of the first line here.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2024-02-07 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 9:02 [RFC 0/3] [gdb/dap] Fix issues triggered by gdb.dap/eof.exp Tom de Vries
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 [this message]
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=87a5occlwb.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).