public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cs120hcc at yahoo dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18861] New: 'reinterpret_cast' in gdb seems to be doing a 'static_cast'.
Date: Fri, 21 Aug 2015 21:27:00 -0000 [thread overview]
Message-ID: <bug-18861-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18861
Bug ID: 18861
Summary: 'reinterpret_cast' in gdb seems to be doing a
'static_cast'.
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: cs120hcc at yahoo dot com
Target Milestone: ---
Created attachment 8544
--> https://sourceware.org/bugzilla/attachment.cgi?id=8544&action=edit
Sample Code and Repro Transcript
Problem: 'reinterpret_cast' in gdb seems to be doing a 'static_cast'.
For example, assume we have two unrelated base classes, 'fred' and 'ginger',
and another class 'hillary' that first extends 'fred' then 'ginger'.
Typically, a 'hillary' object would have the same address as the inherited
'fred' object. The inherited 'ginger' object typically follows the 'fred'
data. (It depends on the compiler implementation, but don't let that distract
you from the description of the gdb bug.)
'reinterpret_cast' typically does not change the value of a pointer that is
casts. Specifically, given 'ginger*' pointer 'g',
'reinterpret_cast<hillary*>(g)' should have the same value as
'static_cast<hillary*>(static_cast<void*>(g))' per 5.2.10.7 of the 2011 and
2014 versions of the C++ standard (N3242 and N4296). Notice that it does work
properly in code generated by g++. However, in the various versions of gdb, it
does not.
The bug is reproduced is several GDB versions and distributions.
> GNU gdb (GDB) 7.4.1-debian installed using apt-get
> GNU gdb (GDB) 7.9.1 downloaded from gnu.org/software/gdb/download/
> GNU gdb (GDB) 7.10.50.20150818-cvs downloaded from gnu.org/software/gdb/download/
> GNU gdb (Gentoo 7.5.1 p2) 7.5.1 installed using portage
Attached is sample code with several transcripts showing the problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-08-21 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 21:27 cs120hcc at yahoo dot com [this message]
2015-08-21 21:27 ` [Bug gdb/18861] " cs120hcc at yahoo dot com
2023-12-23 12:21 ` [Bug c++/18861] " ssbssa at sourceware dot org
2024-03-20 17:02 ` cvs-commit at gcc dot gnu.org
2024-03-20 17:04 ` ssbssa at sourceware dot 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-18861-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).