This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
varobj/1190: Typedef types are not displayed properly
- From: keiths at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 24 Apr 2003 22:04:14 -0000
- Subject: varobj/1190: Typedef types are not displayed properly
- Reply-to: keiths at redhat dot com
>Number: 1190
>Category: varobj
>Synopsis: Typedef types are not displayed properly
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Thu Apr 24 22:08:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: keiths at redhat dot com
>Release: all
>Organization:
>Environment:
>Description:
get_type and get_target_type skip over TYPE_CODE_TYPEDEF.
Consider:
typedef struct _foo Foo;
Foo foo;
The type for "foo" should b" "Foo", not "struct _foo". (Seems to work with non-struct/class typedefs.)
>How-To-Repeat:
Compile attachment. Run in Insight or under MI. Create varobjs for "foo" and "integer". The reported types should be "Foo" and "Integer", not "struct _foo" or "int". Ditto for the pointer types.
>Fix:
Make sure we're not skipping TYPE_CODE_TYPEDEF and not calling CHECK_TYPEDEF for printing type info.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="typedefs.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="typedefs.c"
dHlwZWRlZiBpbnQgSW50ZWdlcjsKdHlwZWRlZiBzdHJ1Y3QgX2Zvbwp7CiAgICBpbnQgYTsKICAg
IGludCBiOwp9IEZvbzsKCmludAptYWluIChpbnQgYXJnYywgY2hhciAqYXJndltdKQp7CiAgICBG
b28gZm9vOwogICAgRm9vICpwX2ZvbzsKICAgIEludGVnZXIgaW50ZWdlcjsKICAgIEludGVnZXIg
KnBfaW50OwogICAgcmV0dXJuIDA7Cn0K