From: Tom Tromey <tom@tromey.com>
To: Paul Koning via Gdb <gdb@sourceware.org>
Cc: Gulshan Singh <gsingh2011@gmail.com>,
Paul Koning <paulkoning@comcast.net>
Subject: Re: `sys.exit` from Python no longer exits the GDB process
Date: Sun, 23 Jun 2024 16:07:23 -0600 [thread overview]
Message-ID: <87tthjwbxg.fsf@tromey.com> (raw)
In-Reply-To: <AED7B9A9-E2A4-4814-AD61-747A6833FA34@comcast.net> (Paul Koning via Gdb's message of "Thu, 20 Jun 2024 15:37:00 -0400")
> If all else fails, os._exit(1) should work, but I too wonder if this
> change is intentional, and if so whether there is a way to control its
> behavior.
I think it's probably just a bug. I feel like we changed some exception
handling stuff, maybe that change was too aggressive. Please file
something in bugzilla -- no guarantees anyone will fix it but at least
that way we have a spot to discuss, etc.
Tom
next prev parent reply other threads:[~2024-06-23 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 19:25 Gulshan Singh via Gdb
2024-06-20 19:37 ` Paul Koning via Gdb
2024-06-23 22:07 ` Tom Tromey [this message]
2024-07-02 19:09 ` Gulshan Singh via Gdb
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=87tthjwbxg.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=gsingh2011@gmail.com \
--cc=paulkoning@comcast.net \
/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