Windbg complaining about sign extension

I’m debugging a 32bit driver issue and dt driver!symbol

is griping like below:

[+0x000] bLength : 0x9 [Type: unsigned char]
VirtualToOffset: 8878f711 not properly sign extended
[+0x001] bDescriptorType : 0x4 [Type: unsigned char]
VirtualToOffset: 8878f712 not properly sign extended
[+0x002] bInterfaceNumber : 0x1 [Type: unsigned char]

Its making it even less pleasant than already is to look at data structures in a crash dump.

Is there any way to disable this? I'm using windbg version: 10.0.15063.468 x86 and have tried x64 version as well.

Thanks

10.016299 doesn’t seem to gripe like that may be you either downgrade
or upgrade windbg

0:000> .shell -ci " dtx ntdll!_EPROCESS @$proc " grep PriorityClass
[+0x17b] PriorityClass : 0x0 [Type: unsigned char]
.shell: Process exited

On 4/19/18, xxxxx@gmail.com wrote:
> I’m debugging a 32bit driver issue and dt driver!symbol is griping
> like below:
>
> [+0x000] bLength : 0x9 [Type: unsigned char]
> VirtualToOffset: 8878f711 not properly sign extended
> [+0x001] bDescriptorType : 0x4 [Type: unsigned char]
> VirtualToOffset: 8878f712 not properly sign extended
> [+0x002] bInterfaceNumber : 0x1 [Type: unsigned char]
>
> Its making it even less pleasant than already is to look at data structures
> in a crash dump.
>
> Is there any way to disable this? I’m using windbg version: 10.0.15063.468
> x86 and have tried x64 version as well.
>
> Thanks
>
>
> —
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
> drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at
> http:
></http:></http:>