Using windbg 6.0.7 with NT4

I was debugging an NT system when it bugchecked. Windbg displayed the
following message (as I expected):

A fatal system error has occurred.

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffbcc159, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : ntoskrnl.exe ( nt!DbgBreakPointWithStatus+4 )

Followup: MachineOwner

I then used “!analyze -v” and it returned immediately with the message “The
debuggee is ready to run”. I then noticed that the message “Kernel symbols
are WRONG”. I’m using the MS symbol server so I didn’t expect this. I
loaded the correct symbols but I still get “The debuggee is ready to run”.

I’m pretty sure that this worked in the previous version of Windbg (4.x).
Does anyone have a clue what might be wrong?

  • Steve -

see my post from 3/20/2002 with the title “!analyze -v behavior/bug?”…
i saw the same behavior on XP with 6.0.7… but haven’t seen it since
(though I haven’t tried to reproduce the same problem since either)…
no answers as of yet though :wink:

sean

Whitman, Steve wrote:

I was debugging an NT system when it bugchecked. Windbg displayed the
following message (as I expected):

A fatal system error has occurred.

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffbcc159, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Probably caused by : ntoskrnl.exe ( nt!DbgBreakPointWithStatus+4 )

Followup: MachineOwner

I then used “!analyze -v” and it returned immediately with the message “The
debuggee is ready to run”. I then noticed that the message “Kernel symbols
are WRONG”. I’m using the MS symbol server so I didn’t expect this. I
loaded the correct symbols but I still get “The debuggee is ready to run”.

I’m pretty sure that this worked in the previous version of Windbg (4.x).
Does anyone have a clue what might be wrong?

  • Steve -

You are currently subscribed to windbg as: xxxxx@stg.com
To unsubscribe send a blank email to %%email.unsub%%

When you see symbol errors try using !sym noisy to see if the places where
the debugger is looking for your symbols makes sense.

!analyze currently runs automatically when the debugger starts for kernel
crash dumps, so you can launch the debugger with the -n option to force
!sym noisy output while !analyze is running.

David Holcomb [MS]