This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi Giovanni,
I'm looking at --debugging* options of objdump.
Which version are you using ?
For some object I'm debugging, I can see a strange debugging type report: Example:
typedef enum { E_A, E_B, E_C } ENUM_E;
typedef struct { ENUM_E e; } STRUCT_S;
debugging report:
typedef struct { enum { E_A, E_B, E_C } e; } STRUCT_S;
For which target is this ?
GCC: (GNU) 3.4.5 20051201 (Red Hat 3.4.5-2) On 32bit Intel machine.
I tried the above test with an i686-pc-cygwin toolchain built from today's mainline GCC sources and mainline binutils sources and I see this output:
typedef enum { E_A, E_B, E_C } ENUM_E; typedef struct %anon1 { /* size 4 */ ENUM_E e; /* bitsize 32, bitpos 0 */ } STRUCT_S;
Sorry, my fault. The reported code it's an intentionally simple example. This happens on a more nested an complex data structure.
typedef struct { %anon120 /* size 2296 */ enum { /* bitsize 32, bitpos 0 */ Q931_PROTDISC_USERSPEC, ... } protDisc; ... };
Thank you, Giovanni
Attachment:
stub.o
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |