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

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/


Before Posting...

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

!analyze -v behavior/bug?

OSR_Community_UserOSR_Community_User Member Posts: 110,217
I was single-stepping through code to get to trace the behavior leading
up to a bugcheck, and noticed a bug (?) with !analyze -v:
---------------snip-----------------------
kd> p
ati2draa!DrvBitBlt+1890:
bff12d1e 8b4850 mov ecx,[eax+0x50]
kd> p
ati2draa!DrvBitBlt+1893:
bff12d21 f781b807000000000080 test dword ptr [ecx+0x7b8],0x80000000
kd> p

*** Fatal System Error: 0x00000050
(0xF000EEF1,0x00000000,0xBFF12D21,0x00000000)

Driver at fault:
*** ati2draa.dll - Address BFF12D21 base at BFF10000, DateStamp 3b7d92ed


A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {f000eef1, 0, bff12d21, 0}

Probably caused by : ati2draa.dll ( ati2draa!DrvBitBlt+1893 )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction:
80579b54 cc int 3
kd> !analyze -v
The debuggee is ready to run
kd> !analyze -v
The debuggee is ready to run
kd> p

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.

BugCheck 50, {f000eef1, 0, bff12d21, 0}

Probably caused by : ati2draa.dll ( ati2draa!DrvBitBlt+1893 )

Followup: MachineOwner
---------

nt!RtlpBreakWithStatusInstruction+1:
80579b55 c20400 ret 0x4
kd> !analyze -v
The debuggee is ready to run

---------------snip-----------------------

Shouldn't "!analyze -v" be able to dump out the bugcheck analysis at
this point? If I let the system go on to generate the full dump of
physical memory, the debugger will break in after the dump is complete
and then "!analyze -v" works as expected... I don't need the analysis
(since I know exactly where and how the problem occurs), but I thought
I'd report this anyways...

Both machines are XP Pro...

sean

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Try "analyzebugcheck -v"

    -----Original Message-----
    From: Sean Bullington [mailto:[email protected]]
    Sent: Wednesday, March 20, 2002 9:46 AM
    To: Kernel Debugging Interest List
    Subject: [windbg] !analyze -v behavior/bug?


    I was single-stepping through code to get to trace the behavior leading
    up to a bugcheck, and noticed a bug (?) with !analyze -v:
    ---------------snip-----------------------
    kd> p
    ati2draa!DrvBitBlt+1890:
    bff12d1e 8b4850 mov ecx,[eax+0x50]
    kd> p
    ati2draa!DrvBitBlt+1893:
    bff12d21 f781b807000000000080 test dword ptr [ecx+0x7b8],0x80000000
    kd> p

    *** Fatal System Error: 0x00000050
    (0xF000EEF1,0x00000000,0xBFF12D21,0x00000000)

    Driver at fault:
    *** ati2draa.dll - Address BFF12D21 base at BFF10000, DateStamp 3b7d92ed


    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    ****************************************************************************
    ***
    *

    *
    * Bugcheck
    Analysis *
    *

    *
    ****************************************************************************
    ***

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {f000eef1, 0, bff12d21, 0}

    Probably caused by : ati2draa.dll ( ati2draa!DrvBitBlt+1893 )

    Followup: MachineOwner
    ---------

    nt!RtlpBreakWithStatusInstruction:
    80579b54 cc int 3
    kd> !analyze -v
    The debuggee is ready to run
    kd> !analyze -v
    The debuggee is ready to run
    kd> p

    A fatal system error has occurred.
    Debugger entered on first try; Bugcheck callbacks have not been invoked.

    A fatal system error has occurred.

    ****************************************************************************
    ***
    *

    *
    * Bugcheck
    Analysis *
    *

    *
    ****************************************************************************
    ***
    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {f000eef1, 0, bff12d21, 0}

    Probably caused by : ati2draa.dll ( ati2draa!DrvBitBlt+1893 )

    Followup: MachineOwner
    ---------

    nt!RtlpBreakWithStatusInstruction+1:
    80579b55 c20400 ret 0x4
    kd> !analyze -v
    The debuggee is ready to run

    ---------------snip-----------------------

    Shouldn't "!analyze -v" be able to dump out the bugcheck analysis at
    this point? If I let the system go on to generate the full dump of
    physical memory, the debugger will break in after the dump is complete
    and then "!analyze -v" works as expected... I don't need the analysis
    (since I know exactly where and how the problem occurs), but I thought
    I'd report this anyways...

    Both machines are XP Pro...

    sean



    ---
    You are currently subscribed to windbg as:
    [email protected]
    To unsubscribe send a blank email to %%email.unsub%%
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    From the docs:

    !analyzebugcheck
    [This is preliminary documentation and subject to change.]

    The !analyzebugcheck extension command is obsolete. Use !analyze instead

    sean

    Joshi, Venu wrote:

    >Try "analyzebugcheck -v"
    >
    >-----Original Message-----
    >From: Sean Bullington [mailto:[email protected]]
    >Sent: Wednesday, March 20, 2002 9:46 AM
    >To: Kernel Debugging Interest List
    >Subject: [windbg] !analyze -v behavior/bug?
    >
    >
    >I was single-stepping through code to get to trace the behavior leading
    >up to a bugcheck, and noticed a bug (?) with !analyze -v:
    >---------------snip-----------------------
    >kd> p
    >ati2draa!DrvBitBlt+1890:
    >bff12d1e 8b4850 mov ecx,[eax+0x50]
    >kd> p
    >ati2draa!DrvBitBlt+1893:
    >bff12d21 f781b807000000000080 test dword ptr [ecx+0x7b8],0x80000000
    >kd> p
    >
    >*** Fatal System Error: 0x00000050
    > (0xF000EEF1,0x00000000,0xBFF12D21,0x00000000)
    >
    >Driver at fault:
    >*** ati2draa.dll - Address BFF12D21 base at BFF10000, DateStamp 3b7d92ed
    >
    >
    >A fatal system error has occurred.
    >Debugger entered on first try; Bugcheck callbacks have not been invoked.
    >
    >A fatal system error has occurred.
    >
    >****************************************************************************
    >***
    >*
    >
    >*
    >* Bugcheck
    >Analysis *
    >*
    >
    >*
    >****************************************************************************
    >***
    >
    >Use !analyze -v to get detailed debugging information.
    >
    >BugCheck 50, {f000eef1, 0, bff12d21, 0}
    >
    >Probably caused by : ati2draa.dll ( ati2draa!DrvBitBlt+1893 )
    >
    >Followup: MachineOwner
    >---------
    >
    >nt!RtlpBreakWithStatusInstruction:
    >80579b54 cc int 3
    >kd> !analyze -v
    >The debuggee is ready to run
    >kd> !analyze -v
    >The debuggee is ready to run
    >kd> p
    >
    >A fatal system error has occurred.
    >Debugger entered on first try; Bugcheck callbacks have not been invoked.
    >
    >A fatal system error has occurred.
    >
    >****************************************************************************
    >***
    >*
    >
    >*
    >* Bugcheck
    >Analysis *
    >*
    >
    >*
    >****************************************************************************
    >***
    >Use !analyze -v to get detailed debugging information.
    >
    >BugCheck 50, {f000eef1, 0, bff12d21, 0}
    >
    >Probably caused by : ati2draa.dll ( ati2draa!DrvBitBlt+1893 )
    >
    >Followup: MachineOwner
    >---------
    >
    >nt!RtlpBreakWithStatusInstruction+1:
    >80579b55 c20400 ret 0x4
    >kd> !analyze -v
    >The debuggee is ready to run
    >
    >---------------snip-----------------------
    >
    >Shouldn't "!analyze -v" be able to dump out the bugcheck analysis at
    >this point? If I let the system go on to generate the full dump of
    >physical memory, the debugger will break in after the dump is complete
    >and then "!analyze -v" works as expected... I don't need the analysis
    >(since I know exactly where and how the problem occurs), but I thought
    >I'd report this anyways...
    >
    >Both machines are XP Pro...
    >
    >sean
    >
    >
    >
    >---
    >You are currently subscribed to windbg as:
    >[email protected]
    >To unsubscribe send a blank email to %%email.unsub%%
    >
    >---
    >You are currently subscribed to windbg as: [email protected]
    >To unsubscribe send a blank email to %%email.unsub%%
    >
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

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!
Writing WDF Drivers 24 January 2022 Live, Online
Internals & Software Drivers 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online
Developing Minifilters 23 May 2022 Live, Online