public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vz-sourceware at zeitlins dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/20091] Breakpoints in @plt routines are almost never useful Date: Tue, 10 Jan 2023 01:34:34 +0000 [thread overview] Message-ID: <bug-20091-4717-35bTo7C9dE@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-20091-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=20091 Vadim Zeitlin <vz-sourceware at zeitlins dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vz-sourceware at zeitlins dot org --- Comment #1 from Vadim Zeitlin <vz-sourceware at zeitlins dot org> --- It would be great if this could be implemented, especially because it seems simple to do it. Would a patch adding an option such as proposed in the first comment above be accepted? The existing workarounds listed e.g. at https://stackoverflow.com/questions/28243549/prevent-plt-procedure-linkage-table-breakpoints-in-gdb are quite unsatisfactory. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-10 1:34 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20091-4717@http.sourceware.org/bugzilla/> 2021-03-17 16:32 ` ssbssa at sourceware dot org 2023-01-10 1:34 ` vz-sourceware at zeitlins dot org [this message] 2023-01-30 10:51 ` aburgess at redhat dot com 2023-02-12 6:21 ` cvs-commit at gcc dot gnu.org 2023-02-12 6:24 ` aburgess at redhat dot com
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-20091-4717-35bTo7C9dE@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: linkBe 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).