dt works, so I will assume that I have made a mistake somewhere, until I
have evidence suggesting otherwise.
– arlie
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Drew Bliss
Sent: Thursday, December 15, 2005 8:57 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Problem with IDebugSymbols3::GetFieldTypeAndOffset
Response from dev:
Could happen, but can’t tell for sure without knowing exact API calls &
struct.
Simple way to verify this is id dt works this will too - ‘dt SOME_STRUCT
SomeField.a’ field offset should be same as one returned by fieldtypeoffset
api call.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Arlie Davis
Sent: Thursday, December 15, 2005 5:46 PM
To: Kernel Debugging Interest List
Subject: [windbg] Problem with IDebugSymbols3::GetFieldTypeAndOffset
I’m having a problem with this method. This is on WinDbg 6.5.3.7. I’m
working on a debugger extension that uses the symbolic info APIs in order to
walk my data structures and interpret and display them. Most everything
works, but I’m hitting a situation where
IDebugSymbols3::GetFieldTypeAndOffset fails.
Or, rather, it returns S_OK, but the FieldTypeId and Offset values are both
zero. FieldTypeId is not accepted by any of the methods that query
information about type IDs, and this is happening on fields that I know are
definitely not at offset zero. So something is failing.
The only thing I can think of is that this is happening on unnamed
structures, that is:
typedef struct _SOME_STRUCT {
struct {
int a;
int b;
…
} SomeField;
} SOME_STRUCT;
Is this a bug, a known limitation, or something else?
Any help is appreciated.
– arlie
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com