public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/21946] Python API search_memory remote targets bug
Date: Wed, 31 Aug 2022 17:53:19 +0000	[thread overview]
Message-ID: <bug-21946-4717-hsJ70sAvW9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21946-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=21946

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
   Target Milestone|---                         |10.1
         Resolution|---                         |FIXED

--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Hannes Domani from comment #5)
> I think that bug was fixed by this commit:
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;
> h=51ac8e22655ba777498249ae0c776fd794a2c298
> 
> Unless it can still be reproduced in gdb 10 or newer.

Thanks.  I'm going to close this, but feel free to
comment or reopen if there is still a bug here.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2022-08-31 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-21946-4717@http.sourceware.org/bugzilla/>
2022-08-31  0:41 ` dominik.b.czarnota+bugzilla at gmail dot com
2022-08-31  1:51 ` tromey at sourceware dot org
2022-08-31 14:56 ` ssbssa at sourceware dot org
2022-08-31 17:53 ` tromey at sourceware dot org [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=bug-21946-4717-hsJ70sAvW9@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).