public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "ks132 at yandex dot ru" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/18601] New: Can't set breakpoint on function with abi_tag attribute Date: Thu, 25 Jun 2015 20:15:00 -0000 [thread overview] Message-ID: <bug-18601-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18601 Bug ID: 18601 Summary: Can't set breakpoint on function with abi_tag attribute Product: gdb Version: 7.9 Status: NEW Severity: normal Priority: P2 Component: c++ Assignee: unassigned at sourceware dot org Reporter: ks132 at yandex dot ru Target Milestone: --- [ks@localhost ~]$ cat test.cpp void f(int) __attribute ((abi_tag ("foo"))); void f(int) { } int main() { f(42); } [ks@localhost ~]$ g++ -g test.cpp [ks@localhost ~]$ [ks@localhost ~]$ nm -C a.out|grep foo 00000000004005b6 T f[abi:foo](int) [ks@localhost ~]$ [ks@localhost ~]$ gdb -q a.out Reading symbols from a.out...done. (gdb) b 'f[abi:foo](int)' No source file named f[abi. Make breakpoint pending on future shared library load? (y or [n]) n (gdb) GCC 5.1 uses abi_tag attribute for Dual ABI implementation: https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html This makes impossible to set breakpoints on some functions with new ABI, which is enabled by default: https://gcc.gnu.org/gcc-5/changes.html#libstdcxx -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-06-25 20:15 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-25 20:15 ks132 at yandex dot ru [this message] 2015-06-25 20:42 ` [Bug c++/18601] " jsweval at arxan dot com 2015-06-29 19:10 ` keiths 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-18601-4717@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).