This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/352: problem with large enum type
- From: rearnsha at arm dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 12 Feb 2002 18:49:49 -0000
- Subject: gdb/352: problem with large enum type
- Reply-to: rearnsha at arm dot com
>Number: 352
>Category: gdb
>Synopsis: problem with large enum type
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Feb 12 10:58:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Richard Earnshaw
>Release: unknown-1.0
>Organization:
>Environment:
arm-netbsd (a.out, stabs)
>Description:
The following program:
enum e {I, J=(unsigned)0xffffffff} e = J;
void dummy() {}
main()
{
dummy();
}
will cause gdb to get confused when asked to print the
value of 'e':
(gdb) p e
$1 = <error type>
(gdb) p &e
$2 = (<unknown type> *) 0x30ac
(gdb) maint print type e
type node 0x1bf480
name '<unknown type>' (0x242fc)
tagname 'e' (0x2026b0)
code 0xe (TYPE_CODE_ERROR)
length 0
upper_bound_type 0x0 (BOUND_SIMPLE)
lower_bound_type 0x0 (BOUND_SIMPLE)
objfile 0x0
target_type 0x0
pointer_type 0x0
reference_type 0x0
cv_type 0x1bf480
as_type 0x1bf480
flags 0x0
nfields 0 0x0
vptr_basetype 0x0
vptr_fieldno -1
type_specific 0x0
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: