From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/dap] Fix exit race
Date: Fri, 23 Feb 2024 14:08:40 -0700 [thread overview]
Message-ID: <87zfvqx50n.fsf@tromey.com> (raw)
In-Reply-To: <87sf1jxggn.fsf@tromey.com> (Tom Tromey's message of "Fri, 23 Feb 2024 10:01:28 -0700")
Tom> I tried adding send_gdb("quit") to Server.main_loop, but of course this
Tom> just reintroduces the crash here. But I tend to think this would be the
Tom> right thing to do, and so adding some kind of special case in gdb's
Tom> Python layer would be appropriate.
I've got a series to clean this up that I will send in a moment.
Tom
prev parent reply other threads:[~2024-02-23 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 15:01 Tom de Vries
2024-02-13 18:10 ` Tom Tromey
2024-02-14 15:39 ` Tom de Vries
2024-02-14 15:46 ` Tom Tromey
2024-02-23 17:01 ` Tom Tromey
2024-02-23 21:08 ` 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=87zfvqx50n.fsf@tromey.com \
--to=tromey@adacore.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).