public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "keiths at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/18601] Can't set breakpoint on function with abi_tag attribute Date: Mon, 29 Jun 2015 19:10:00 -0000 [thread overview] Message-ID: <bug-18601-4717-DmAUN7Fk7F@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18601-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18601 Keith Seitz <keiths at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keiths at redhat dot com --- Comment #1 from Keith Seitz <keiths at redhat dot com> --- I hope to be working up a formal fix for this in the coming week, but I'd like to mention a few things, including a workaround. First, explicit locations (coming to a release some after 7.10 I suspect) "just work": (gdb) break -function f[abi:foo] Breakpoint 1 at 0x4005bd: file /home/keiths/tmp/18601.cc, line 4. Not that it will help you for the meantime (unless you apply my monstrously large locations API patches). I'll be returning to that series of patches this week, too. An aside: quote-enclosing (entire) linespecs does /nothing/ in the parser. Because IDEs have historically quote-enclosed all linespec locations, the parser has to ignore them. Another historical bug that we have to maintain. That's /not/ to say that quotes do nothing. As it is, I happen to know that there is another legacy bug that the linespec parser emulates that can be used to workaround your problem: (gdb) b 'f[abi:foo]':1 Breakpoint 1 at 0x4005bd: file /home/keiths/tmp/18601.cc, line 4. [The :1 should be a line-offset from the beginning of the function. That feature was never implemented, but since it was silently ignored in previous releases, that behavior was maintained when the linespec parser was rewritten.] -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2015-06-29 19:10 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-25 20:15 [Bug c++/18601] New: " ks132 at yandex dot ru 2015-06-25 20:42 ` [Bug c++/18601] " jsweval at arxan dot com 2015-06-29 19:10 ` keiths at redhat dot com [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-18601-4717-DmAUN7Fk7F@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).