Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Windbg complaining about sign extension

wdwd Member - All Emails Posts: 32
I'm debugging a 32bit driver issue and dt driver!symbol <address> 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

Comments

  • raj_rraj_r Member - All Emails Posts: 983
    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, [email protected] <[email protected]> wrote:
    > I'm debugging a 32bit driver issue and dt driver!symbol <address> 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://www.osr.com/seminars&gt;
    >
    > To unsubscribe, visit the List Server section of OSR Online at
    > <http://www.osronline.com/page.cfm?name=ListServer&gt;
    >
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 15 Jun 2020 LIVE ONLINE
Writing WDF Drivers 22 June 2020 LIVE ONLINE
Internals & Software Drivers 28 Sept 2020 Dulles, VA