public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sivachandra at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/13403] invalid vptr after gdb prints the return value of a virtual function member on x86_64 system
Date: Wed, 18 Jun 2014 12:52:00 -0000 [thread overview]
Message-ID: <bug-13403-4717-B0p8AxJw53@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13403-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13403
Siva Chandra <sivachandra at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sivachandra at google dot com
--- Comment #1 from Siva Chandra <sivachandra at google dot com> ---
I think the source of the problem is bad calling convention.
FWIW, amd64-tdep.c does not align with
http://mentorembedded.github.io/cxx-abi/abi.html#return-value. I do not think
the fix is straight forward (consider c++11 with =default annotations on the
destructors and constructors which is not emitted in the DWARF by gcc
currently). One could probably come up with a fix which can improve the
situation but not fix this problem thoroughly.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-06-18 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 12:43 [Bug c++/13403] New: " zbojthe at urdeso dot hu
2011-11-11 12:44 ` [Bug c++/13403] " zbojthe at urdeso dot hu
2011-12-15 8:45 ` zbojthe at urdeso dot hu
2012-03-15 12:18 ` gbenson at redhat dot com
2014-06-18 12:52 ` sivachandra at google dot com [this message]
2014-06-18 13:14 ` gbenson at redhat dot com
2014-10-15 11:41 ` cvs-commit 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-13403-4717-B0p8AxJw53@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).