From: Fernando Nasser <fnasser@redhat.com>
To: gdb@sources.redhat.com, Andrew Cagney <cagney@cygnus.com>,
Chris Faylor <cgf@cygnus.com>
Subject: Re: Warning: something weird with void* types.
Date: Thu, 10 May 2001 09:46:00 -0000 [thread overview]
Message-ID: <3AFAC56E.9AF1DD27@redhat.com> (raw)
In-Reply-To: <3AF6D9F3.ADD7A779@redhat.com>
I can't believe nobody has anything to say about this...
Fernando Nasser wrote:
>
> FYI, we are having to make a change in Insight to cope with a funny
> thing that recently appeared in GDB.
>
> The target type of a void* does not have the type name set to "void" any
> longer.
>
> (gdb) p *type
> $3 = {code = TYPE_CODE_PTR, name = 0x0, tag_name = 0x0, length = 4,
> upper_bound_type = 0, lower_bound_type = 0, objfile = 0x854e998,
> target_type = 0x8bcd5d8, pointer_type = 0x0, reference_type = 0x0,
> cv_type = 0x8bcd61c, flags = 1, nfields = 0, fields = 0x0,
> vptr_basetype = 0x0, vptr_fieldno = -1, type_specific = {arg_types =
> 0x0,
> cplus_stuff = 0x0}}
> (gdb) p *target
> $4 = {code = TYPE_CODE_VOID, name = 0x0, tag_name = 0x0, length = 1,
> upper_bound_type = 0, lower_bound_type = 0, objfile = 0x854e998,
> target_type = 0x0, pointer_type = 0x8bcd61c, reference_type = 0x0,
> cv_type = 0x8bcd5d8, flags = 0, nfields = 0, fields = 0x0,
> vptr_basetype = 0x0, vptr_fieldno = -1, type_specific = {arg_types =
> 0x0,
> cplus_stuff = 0x0}}
>
> As you see, TYPE_CODE_VOID does not have a name anymore, at least when
> it is the target of a (void *) type..
>
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-05-10 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 10:25 Fernando Nasser
2001-05-10 9:46 ` Fernando Nasser [this message]
2001-05-10 10:00 ` Elena Zannoni
2001-05-16 8:21 ` Daniel Berlin
2001-05-18 10:30 ` Fernando Nasser
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=3AFAC56E.9AF1DD27@redhat.com \
--to=fnasser@redhat.com \
--cc=cagney@cygnus.com \
--cc=cgf@cygnus.com \
--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