This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/18601] Can't set breakpoint on function with abi_tag attribute


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]