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 c++/27539] New: FAIL: gdb.cp/typeid.exp: before starting: print &typeid(i)
Date: Sun, 07 Mar 2021 10:30:02 +0000 [thread overview]
Message-ID: <bug-27539-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27539
Bug ID: 27539
Summary: FAIL: gdb.cp/typeid.exp: before starting: print
&typeid(i)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: c++
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On openSUSE tumbleweed, I run into:
...
FAIL: gdb.cp/typeid.exp: before starting: print &typeid(i)
FAIL: gdb.cp/typeid.exp: before starting: print &typeid(i) ==
&typeid(typeof(i))
FAIL: gdb.cp/typeid.exp: before starting: print &typeid(cp)
FAIL: gdb.cp/typeid.exp: before starting: print &typeid(cp) ==
&typeid(typeof(cp))
FAIL: gdb.cp/typeid.exp: before starting: print &typeid(ccp)
FAIL: gdb.cp/typeid.exp: before starting: print &typeid(ccp) ==
&typeid(typeof(ccp))
...
The first in more detail:
...
(gdb) file typeid^M
Reading symbols from typeid...^M
(gdb) print &typeid(i)^M
could not find typeinfo symbol for 'int'^M
(gdb) FAIL: gdb.cp/typeid.exp: before starting: print &typeid(i)
...
Easily reproduced on command line using:
...
$ gdb -batch ./outputs/gdb.cp/typeid/typeid -ex "print typeid (int)"
could not find typeinfo symbol for 'int'
...
Interestingly though, if we first start, we get::
...
$ gdb -batch ./outputs/gdb.cp/typeid/typeid -ex start -ex "print typeid (int)"
Temporary breakpoint 1 at 0x40112a: file typeid.cc, line 52.
Temporary breakpoint 1, main () at typeid.cc:52
52 const std::type_info &xi = typeid(i);
$1 = {_vptr.type_info = 0x7ffff7fa0218 <vtable for
__cxxabiv1::__fundamental_type_info+16>, __name = 0x7ffff7f31554 <typeinfo name
for int> "i"}
...
In the latter case we get the minimal symbol from:
...
$ readelf -r /usr/lib64/libstdc++.so.6.0.29 | c++filt | grep "typeinfo for int"
00000020a710 04d300000001 R_X86_64_64 000000000020a738 typeinfo for
int@@CXXABI_1.3 + 0
00000020a730 04d300000001 R_X86_64_64 000000000020a738 typeinfo for
int@@CXXABI_1.3 + 0
...
While in the former case we fail to find the minimal symbol:
...
$ readelf -r ./outputs/gdb.cp/typeid/typeid | c++filt | grep "typeinfo for int"
000000403c20 000a00000005 R_X86_64_COPY 0000000000403c20 typeinfo for
int@CXXABI_1.3 + 0
...
The only difference I notice is '@@' vs '@'.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-07 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 10:30 vries at gcc dot gnu.org [this message]
2021-11-22 13:57 ` [Bug c++/27539] " vries at gcc dot gnu.org
2024-03-27 7:00 ` 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-27539-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: link
Be 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).