public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/29138] [gdb/testsuite] FAIL: gdb.cp/break-f-std-string.exp: _GLIBCXX_USE_CXX11_ABI=1: whatis /r std::string Date: Tue, 10 May 2022 15:22:33 +0000 [thread overview] Message-ID: <bug-29138-4717-26iUpkddGd@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29138-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29138 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |palves at sourceware dot org --- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> --- So, with gcc-8, I have: ... $ gdb -q -batch outputs/gdb.cp/break-f-std-string/break-f-std-string-1.o -ex "set language c++" -ex "whatis /r std::string" No symbol "string" in namespace "std". ... but using std::__cxx11::string instead works: ... $ gdb -q -batch outputs/gdb.cp/break-f-std-string/break-f-std-string-1.o -ex "set language c++" -ex "whatis /r std::__cxx11::string" type = std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > ... Whereas with gcc-9, I have instead a failure using std::__cxx11::string: ... $ gdb -q -batch outputs/gdb.cp/break-f-std-string/break-f-std-string-1.o -ex "set language c++" -ex "whatis /r std::__cxx11::string" No symbol "string" in namespace "std::__cxx11". ... and using std::string works: ... $ gdb -q -batch outputs/gdb.cp/break-f-std-string/break-f-std-string-1.o -ex "set language c++" -ex "whatis /r std::string" type = std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-10 15:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-10 14:57 [Bug testsuite/29138] New: " vries at gcc dot gnu.org 2022-05-10 15:22 ` vries at gcc dot gnu.org [this message] 2022-05-10 16:26 ` [Bug testsuite/29138] " vries at gcc dot gnu.org 2022-05-11 12:36 ` pedro at palves dot net 2022-05-11 12:37 ` pedro at palves dot net 2022-05-12 11:47 ` vries at gcc dot gnu.org 2022-05-12 13:01 ` vries at gcc dot gnu.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-29138-4717-26iUpkddGd@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).