From: "Sp3cial K" <ikiwibebe@hotmail.com>
To: drow@false.org
Cc: gdb@sources.redhat.com
Subject: Re: gdb cannot print object casted to a pointer of certain class
Date: Tue, 08 Nov 2005 00:04:00 -0000 [thread overview]
Message-ID: <BAY105-F3222B51A6F15F6C4D18AC9BA640@phx.gbl> (raw)
In-Reply-To: <20051103212218.GA11828@nevyn.them.org>
I dont have the code with me right now. What I remember is that the class
has a valid constructor, and it works fine if I add "class" in front of the
name to force it to be read as a class. Do you think this is the frame or
symbol table problem?
>From: Daniel Jacobowitz <drow@false.org>
>To: Sp3cial K <ikiwibebe@hotmail.com>
>CC: gdb@sources.redhat.com
>Subject: Re: gdb cannot print object casted to a pointer of certain class
>Date: Thu, 3 Nov 2005 16:22:18 -0500
>
>On Wed, Nov 02, 2005 at 07:04:45PM -0500, Sp3cial K wrote:
> > Has anyone encountered a problem where ptype prints out the class info
>in
> > most frames, but it complaints "Type xxx has no component named xxx." in
> > one frame? Ironically, the frame where it doesn't print out correctly
>is
> > in a function of that class!
>
>The more details you snip out of a bug report, the less likely it is
>that we can help you. But I believe I know what this problem is:
>
> > Also, when I tried to print out an object casted to that class, as
>follows:
> > p *(xxx *)0x12345678
> > it complains:
> > A parse error in expression, near `)0x12345678'
>
>The name is being interpreted differently in that scope, probably as
>the constructor rather than the class. A testcase might let us fix
>this.
>
>--
>Daniel Jacobowitz
>CodeSourcery, LLC
prev parent reply other threads:[~2005-11-08 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 0:04 Sp3cial K
2005-11-03 21:22 ` Daniel Jacobowitz
2005-11-08 0:04 ` Sp3cial K [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=BAY105-F3222B51A6F15F6C4D18AC9BA640@phx.gbl \
--to=ikiwibebe@hotmail.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/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).