* Warning: something weird with void* types.
@ 2001-05-07 10:25 Fernando Nasser
2001-05-10 9:46 ` Fernando Nasser
0 siblings, 1 reply; 5+ messages in thread
From: Fernando Nasser @ 2001-05-07 10:25 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Warning: something weird with void* types.
2001-05-07 10:25 Warning: something weird with void* types Fernando Nasser
@ 2001-05-10 9:46 ` Fernando Nasser
2001-05-10 10:00 ` Elena Zannoni
2001-05-16 8:21 ` Daniel Berlin
0 siblings, 2 replies; 5+ messages in thread
From: Fernando Nasser @ 2001-05-10 9:46 UTC (permalink / raw)
To: gdb, Andrew Cagney, Chris Faylor
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Warning: something weird with void* types.
2001-05-10 9:46 ` Fernando Nasser
@ 2001-05-10 10:00 ` Elena Zannoni
2001-05-16 8:21 ` Daniel Berlin
1 sibling, 0 replies; 5+ messages in thread
From: Elena Zannoni @ 2001-05-10 10:00 UTC (permalink / raw)
To: Fernando Nasser; +Cc: gdb, Andrew Cagney, Chris Faylor
Fernando Nasser writes:
> I can't believe nobody has anything to say about this...
Can you file a PR? So we don't forget about this.
Elena
>
>
> 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
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Warning: something weird with void* types.
2001-05-10 9:46 ` Fernando Nasser
2001-05-10 10:00 ` Elena Zannoni
@ 2001-05-16 8:21 ` Daniel Berlin
2001-05-18 10:30 ` Fernando Nasser
1 sibling, 1 reply; 5+ messages in thread
From: Daniel Berlin @ 2001-05-16 8:21 UTC (permalink / raw)
To: Fernando Nasser, gdb, Andrew Cagney, Chris Faylor
--On Thursday, May 10, 2001 12:44 PM -0400 Fernando Nasser
<fnasser@redhat.com> wrote:
> I can't believe nobody has anything to say about this...
Well, a quick looksie shows the only thing that could be causing this that
i immediately see is in stabsread.c
You are using STABS, I assume, right?
Can you verify it doesn't occur with DWARF2, so I can generate a fix for
the problem, or if it does occur with DWARF2, look elsewhere?
>
>
> 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Warning: something weird with void* types.
2001-05-16 8:21 ` Daniel Berlin
@ 2001-05-18 10:30 ` Fernando Nasser
0 siblings, 0 replies; 5+ messages in thread
From: Fernando Nasser @ 2001-05-18 10:30 UTC (permalink / raw)
To: Daniel Berlin; +Cc: Fernando Nasser, gdb, Andrew Cagney, Chris Faylor
Daniel Berlin wrote:
>
> --On Thursday, May 10, 2001 12:44 PM -0400 Fernando Nasser
> <fnasser@redhat.com> wrote:
>
> > I can't believe nobody has anything to say about this...
>
> Well, a quick looksie shows the only thing that could be causing this that
> i immediately see is in stabsread.c
>
> You are using STABS, I assume, right?
>
> Can you verify it doesn't occur with DWARF2, so I can generate a fix for
> the problem, or if it does occur with DWARF2, look elsewhere?
>
Dan,
I am currently on a trip and with very limited access to my stuff and I
will only be back Tuesday.
But I reproduced this problem on Linux debugging GDB with itself.
Cheers,
Fernando
> >
> >
> > 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
--
Fernando Nasser
Red Hat Canada Ltd.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-05-18 10:30 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-05-07 10:25 Warning: something weird with void* types Fernando Nasser
2001-05-10 9:46 ` Fernando Nasser
2001-05-10 10:00 ` Elena Zannoni
2001-05-16 8:21 ` Daniel Berlin
2001-05-18 10:30 ` Fernando Nasser
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox