public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/32079] Can't insert internal breakpoints after inferior dlclose some share objects
Date: Fri, 30 Aug 2024 11:22:30 +0000 [thread overview]
Message-ID: <bug-32079-4717-NnsAq52Ovc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-32079-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=32079
Andrew Burgess <aburgess at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aburgess at redhat dot com
--- Comment #5 from Andrew Burgess <aburgess at redhat dot com> ---
I've posted a proposed fix for this bug here:
https://inbox.sourceware.org/gdb-patches/cover.1724948606.git.aburgess@redhat.com/
It is inspired by the changes Hannes Domani proposed in:
https://sourceware.org/bugzilla/show_bug.cgi?id=32079#c3
But when combined with an earlier patch in the series I don't think the
delete_breakpoint call is needed. And as Tom pointed out I handle more b/p
types as well as fixing another issue that cropped up during testing.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-08-30 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 13:16 [Bug breakpoints/32079] New: " blarsen at redhat dot com
2024-08-14 12:19 ` [Bug breakpoints/32079] " ssbssa at sourceware dot org
2024-08-14 13:11 ` blarsen at redhat dot com
2024-08-16 19:42 ` ssbssa at sourceware dot org
2024-08-19 20:36 ` woodard at redhat dot com
2024-08-23 17:06 ` tromey at sourceware dot org
2024-08-30 11:22 ` aburgess at redhat dot com [this message]
2025-02-24 11:02 ` cvs-commit at gcc dot gnu.org
2025-02-24 11:02 ` cvs-commit at gcc dot gnu.org
2025-02-24 11:03 ` cvs-commit at gcc dot gnu.org
2025-02-24 16:35 ` aburgess at redhat dot com
2025-02-24 17:08 ` ssbssa at sourceware dot org
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-32079-4717-NnsAq52Ovc@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).