From: Pedro Alves <pedro@palves.net>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v4 0/6] Fix some Python Inferior methods
Date: Fri, 14 Jul 2023 19:09:55 +0100 [thread overview]
Message-ID: <d607daee-f180-815b-ecbd-cb7e39d75dcd@palves.net> (raw)
In-Reply-To: <20230714-py-inf-fixes-30615-v4-0-9189744d8547@adacore.com>
On 2023-07-14 18:06, Tom Tromey wrote:
> A user pointed out a bug in Inferior.search_memory. This series is
> the result. Most of the patches are minor things I noticed while
> working on the final patch, which fixes the bug.
>
> Regression tested on x86-64 Fedora 36.
For whole series:
Approved-By: Pedro Alves <pedro@palves.net>
Thanks.
prev parent reply other threads:[~2023-07-14 18:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 17:06 Tom Tromey
2023-07-14 17:06 ` [PATCH v4 1/6] Minor cleanups in py-inferior.exp Tom Tromey
2023-07-14 17:06 ` [PATCH v4 2/6] Refactor py-inferior.exp Tom Tromey
2023-07-14 17:06 ` [PATCH v4 3/6] Rename Python variable in py-inferior.exp Tom Tromey
2023-07-14 17:06 ` [PATCH v4 4/6] Remove obsolete comment from gdbthread.h Tom Tromey
2023-07-14 17:06 ` [PATCH v4 5/6] Introduce scoped_restore_current_inferior_for_memory Tom Tromey
2023-07-14 17:06 ` [PATCH v4 6/6] Use correct inferior in Inferior.read_memory et al Tom Tromey
2023-07-15 13:31 ` Andrew Burgess
2023-07-17 17:12 ` Tom Tromey
2023-07-17 18:15 ` Pedro Alves
2023-07-17 18:44 ` Tom Tromey
2023-07-18 12:20 ` [PATCH] Fix gdb.Inferior.read_memory without execution (PR dap/30644) (was: Re: [PATCH v4 6/6] Use correct inferior in Inferior.read_memory et al) Pedro Alves
2023-07-18 17:25 ` [PATCH] Fix gdb.Inferior.read_memory without execution (PR dap/30644) Tom Tromey
2023-07-19 13:14 ` Pedro Alves
2023-07-18 8:48 ` [PATCH v4 6/6] Use correct inferior in Inferior.read_memory et al Aktemur, Tankut Baris
2023-07-18 12:26 ` Pedro Alves
2023-07-18 13:19 ` Aktemur, Tankut Baris
2023-07-14 18:09 ` Pedro Alves [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=d607daee-f180-815b-ecbd-cb7e39d75dcd@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.com \
/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).