WinDbg 5.00.2195.1 problems

NTFSD
1

Target machine: NT4 without any SPs and patches.

  1. Very nasty. Unable to break the execution of the running kernel. Both the
    Break toolbar button and Ctrl-C lead to:
    DMKD: Sending breakin packet…
    message. The target stalls, but WinDbg NEVER considers it stalled and
    commands like “k” fail with
    Cannot issue this command while target system is running
    message.
    However, “Break on initial breakpoint” setting works. Debug prints work OK
    too.
    “!list” command shows that WinDbg picked W2K extension DLL instead of NT4
    one. Is there any way to specify explicitly that NT4 extension DLL must be
    loaded, not W2K?
    I have tried to force WinDbg to load the NT4 DLL by renaming directories -
    this did not cure the Ctrl-C problem.
    WinDbg 5.00.1999 is free from this problem.
  2. Unable to save color layout and re-use it at next WinDbg startup - is it
    OK?
  3. “k” command and Call Stack window always shows stack data expanded to 64
    bit - is it OK? Can it be switched off (to 32 bit)?
  4. Sometimes (reproducable rather good) WinDbg forgets to rebase the
    NTOSKRNL symbols. The symbol values end up being 0x0000xxxx instead of
    0x8000xxxx. This leads to unusable symbols.

Maxim Shatskih
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com

2

Hi,

Did you ever resolve this problem ? I am experiencing something similar.

Sara

-----Original Message-----
From: Maxim S. Shatskih
To: File Systems Developers
Date: Friday, July 14, 2000 12:36 AM
Subject: [ntfsd] WinDbg 5.00.2195.1 problems

> Target machine: NT4 without any SPs and patches.
>
>1) Very nasty. Unable to break the execution of the running kernel. Both
the
>Break toolbar button and Ctrl-C lead to:
> DMKD: Sending breakin packet…
>message. The target stalls, but WinDbg NEVER considers it stalled and
>commands like “k” fail with
> Cannot issue this command while target system is running
>message.
>However, “Break on initial breakpoint” setting works. Debug prints work OK
>too.
>“!list” command shows that WinDbg picked W2K extension DLL instead of NT4
>one. Is there any way to specify explicitly that NT4 extension DLL must be
>loaded, not W2K?
>I have tried to force WinDbg to load the NT4 DLL by renaming directories -
>this did not cure the Ctrl-C problem.
>WinDbg 5.00.1999 is free from this problem.
>2) Unable to save color layout and re-use it at next WinDbg startup - is it
>OK?
>3) “k” command and Call Stack window always shows stack data expanded to 64
>bit - is it OK? Can it be switched off (to 32 bit)?
>4) Sometimes (reproducable rather good) WinDbg forgets to rebase the
>NTOSKRNL symbols. The symbol values end up being 0x0000xxxx instead of
>0x8000xxxx. This leads to unusable symbols.
>
>Maxim Shatskih
>StorageCraft Corporation
>xxxxx@storagecraft.com
>http://www.storagecraft.com
>
>
>
>
>—
>You are currently subscribed to ntfsd as: xxxxx@veritas.com
>To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>

3

No, I moved to the WinHEC WinDbg which is the one which uses the
command-line KD code. The latest one.
The only problem I experience with the latter one is - no “Stop on Initial
Breakpoint” functionality.

Max

----- Original Message -----
From: Sara Abraham
To: File Systems Developers
Sent: Wednesday, July 19, 2000 12:02 AM
Subject: [ntfsd] Re: WinDbg 5.00.2195.1 problems

> Hi,
>
> Did you ever resolve this problem ? I am experiencing something similar.
>
> Sara
>
> -----Original Message-----
> From: Maxim S. Shatskih
> To: File Systems Developers
> Date: Friday, July 14, 2000 12:36 AM
> Subject: [ntfsd] WinDbg 5.00.2195.1 problems
>
>
> > Target machine: NT4 without any SPs and patches.
> >
> >1) Very nasty. Unable to break the execution of the running kernel. Both
> the
> >Break toolbar button and Ctrl-C lead to:
> > DMKD: Sending breakin packet…
> >message. The target stalls, but WinDbg NEVER considers it stalled and
> >commands like “k” fail with
> > Cannot issue this command while target system is running
> >message.
> >However, “Break on initial breakpoint” setting works. Debug prints work
OK
> >too.
> >“!list” command shows that WinDbg picked W2K extension DLL instead of NT4
> >one. Is there any way to specify explicitly that NT4 extension DLL must
be
> >loaded, not W2K?
> >I have tried to force WinDbg to load the NT4 DLL by renaming
directories -
> >this did not cure the Ctrl-C problem.
> >WinDbg 5.00.1999 is free from this problem.
> >2) Unable to save color layout and re-use it at next WinDbg startup - is
it
> >OK?
> >3) “k” command and Call Stack window always shows stack data expanded to
64
> >bit - is it OK? Can it be switched off (to 32 bit)?
> >4) Sometimes (reproducable rather good) WinDbg forgets to rebase the
> >NTOSKRNL symbols. The symbol values end up being 0x0000xxxx instead of
> >0x8000xxxx. This leads to unusable symbols.
> >
> >Maxim Shatskih
> >StorageCraft Corporation
> >xxxxx@storagecraft.com
> >http://www.storagecraft.com
> >
> >
> >
> >
> >—
> >You are currently subscribed to ntfsd as: xxxxx@veritas.com
> >To unsubscribe send a blank email to $subst(‘Email.Unsub’)
> >
>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>