From: Tom Tromey <tom@tromey.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Tom Tromey <tom@tromey.com>,
Florian Weimer via Gdb <gdb@sourceware.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: Using GDB as a Python interpreter
Date: Mon, 03 Jul 2023 17:00:46 -0600 [thread overview]
Message-ID: <871qhoeh29.fsf@tromey.com> (raw)
In-Reply-To: <20230703202421.GA11693@gnu.wildebeest.org> (Mark Wielaard's message of "Mon, 3 Jul 2023 22:24:21 +0200")
Mark> Was that this?
Mark> https://inbox.sourceware.org/gdb-patches/20190721235427.21893-1-kevinb@redhat.com/
Yeah, and I mis-remembered who sent it upstream, sorry about that!
Tom
prev parent reply other threads:[~2023-07-03 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 8:53 Florian Weimer
2023-07-03 7:11 ` Aktemur, Tankut Baris
2023-07-03 8:13 ` Florian Weimer
2023-07-03 19:39 ` Tom Tromey
2023-07-03 20:24 ` Mark Wielaard
2023-07-03 23:00 ` 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=871qhoeh29.fsf@tromey.com \
--to=tom@tromey.com \
--cc=fweimer@redhat.com \
--cc=gdb@sourceware.org \
--cc=mark@klomp.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).