From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/python] Document quit_force uses
Date: Thu, 27 Aug 2026 09:56:59 -0600 [thread overview]
Message-ID: <87fqzza75g.fsf@tromey.com> (raw)
In-Reply-To: <20260811080018.1151006-1-tdevries@suse.de> (Tom de Vries's message of "Tue, 11 Aug 2026 10:00:18 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> The Python extension has two functions that convert exceptions from the GDB
Tom> domain to the Python domain and vice versa: gdbpy_convert_exception and
Tom> gdbpy_handle_exception.
Tom> Each function has an exception though, where it calls quit_force:
Tom> - for gdbpy_convert_exception, when handling gdb_exception_forced_quit, and
Tom> - for gdbpy_handle_exception, when handling SystemExit.
Tom> I think it's a good idea to document these exceptions in more detail, and
Tom> since AFAICT the reasoning is the same, I've added the same comment in both
Tom> places.
Ok.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2026-08-27 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 8:00 Tom de Vries
2026-08-27 7:50 ` [PING][PATCH] " Tom de Vries
2026-08-27 15:56 ` Tom Tromey [this message]
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=87fqzza75g.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