From: <Paul_Koning@Dell.com>
Cc: <gdb@sourceware.org>
Subject: Re: Types mangled when using "file -readnow <filename>"
Date: Thu, 06 Sep 2012 18:46:00 -0000 [thread overview]
Message-ID: <C75A84166056C94F84D238A44AF9F6AD1FF53A@AUSX10MPC103.AMER.DELL.COM> (raw)
In-Reply-To: <C75A84166056C94F84D238A44AF9F6AD1FED8D@AUSX10MPC103.AMER.DELL.COM>
On Sep 6, 2012, at 12:16 PM, <Paul_Koning@Dell.com>
<Paul_Koning@Dell.com> wrote:
> I noticed a strange problem when doing some Python scripting in which I open the execfile with the "-readnow" switch: Some structures (C++ classes, actually) lose their fields when I do that.
>
> If I open the file without -readnow, and I do a "ptype", I see a base class, a data member, and a static method.
>
> If I open the file with -readnow, ptype shows only the static method, and omits both the base class and the data member.
>
> This is GDB 7.3.1, reading binaries produced by GCC 4.5.4 and Binutils 2.20.1. Is this a known problem? Fixed in a later release?
>
> paul
>
After further investigation, this turns out to be due to incorrect debug data emitted by GCC 4.*. I'll report it there.
paul
prev parent reply other threads:[~2012-09-06 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 16:16 Paul_Koning
2012-09-06 18:46 ` Paul_Koning [this message]
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=C75A84166056C94F84D238A44AF9F6AD1FF53A@AUSX10MPC103.AMER.DELL.COM \
--to=paul_koning@dell.com \
--cc=gdb@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).