Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

!analyze not working

2,892 views
Skip to first unread message

Dominic Hopton

unread,
Apr 1, 2003, 1:57:13 PM4/1/03
to
I've just installed WinDBG on Both my desktop (winXP-SP1) and test server
(Win2k3/3763), and I can't get !analyze to work anymore. It used to work on
my desktop, but I tried it about 2 weeks ago, and it wasnt working. I
upgraded to 6.1.0017.2, and it still didnt work. I'm looking at full memory
dumps from a win2k SP3 & SP4 beta machine.

When I run !analyze, I get:
0: kd> !analyze
No export analyze found

Repro:
Start WinDBG
File, Open Crash Dump
type !analyze at the KD> prompt

Any pointers, comments?

Yours,
Dominic


Ivan Brugiolo [MSFT]

unread,
Apr 1, 2003, 6:38:32 PM4/1/03
to
can you do a ".chain" in you debugger ?
Looks like the debugger has "lost" the path to the default extensions

you can alway load them with a fully qualified command
kd>!c:\debuggers\winxp\extension.comman

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"Dominic Hopton" <domini...@hotmail.com> wrote in message
news:eGU9LNK#CHA....@TK2MSFTNGP12.phx.gbl...

Dominic Hopton

unread,
Apr 2, 2003, 4:35:56 AM4/2/03
to
0: kd> !chain
Default extension DLLs are not loaded until after initial connection


This is performing the same steps that I posted in my original post. I'm 99%
sure I didnt need to do anything extra.

This happens on my desktop (filled with *stuff*) and my server, which is
only running IIS - nothing else installed. It was installed from the web
with the defaults during setup.

"Ivan Brugiolo [MSFT]" <ivan...@online.microsoft.com> wrote in message
news:OhWnNfK#CHA...@TK2MSFTNGP12.phx.gbl...

Ivan Brugiolo [MSFT]

unread,
Apr 2, 2003, 10:50:55 AM4/2/03
to
When the target boots up, are you seeing messages like these in the debugger
?
I also reported the output of '.chain' ( dot, not bang)

////////////////////////////////////////////////////////////////////////////
//////////////////////////////
Microsoft (R) Windows Debugger Version 6.X.0005.3
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \\.\com5
Waiting to reconnect...
Connected to WindowsYYYY XXXX x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: D:\WINDOWS\symbols
Executable search path is:
vertarget
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntoskrnl.exe -
WindowsXXXX Kernel Version YYYY UP Free x86 compatible
Product: Server, suite: Enterprise TerminalServer DataCenter SingleUserTS
Built by: XXXX.YYYY.030331-2000
Kernel base = 0x804e3000 PsLoadedModuleList = 0x8057ce48
Debug session time: Tue Apr 01 19:00:40 2003
System Uptime: 0 days 7:03:52.468
////////////////////////////////////////////////////////////////////////////
//////////////////////////////

1: kd> .chain
Extension DLL search Path:
D:\Program Files\Debugging Tools for Windows\winext;D:\Program
Files\Debugging Tools for Windows\WINXP;D:
Program Files\Debugging Tools for Windows\pri;D:\Program Files\Debugging
Tools for Windows;D:\WINDOWS\system3
;D:\WINDOWS;D:\WINDOWS\system32\WBEM;D:\Program Files\Debugging Tools for
Windows;
Extension DLL chain:
exts: image 6.X.0005.0, API 1.0.0, built Fri Mar 07 19:06:04 2003
[path: D:\Program Files\Debugging Tools for Windows\WINXP\exts.dll]
kext: image 6.X.0005.0, API 1.0.0, built Fri Mar 07 19:06:07 2003
[path: D:\Program Files\Debugging Tools for Windows\winext\kext.dll]
kdexts: image 6.X.4008.0, API 1.0.0, built Fri Mar 07 11:24:09 2003
[path: D:\Program Files\Debugging Tools for
Windows\WINXP\kdexts.dll]
dbghelp: image 6.X.0005.0, API 6.0.6, built Fri Mar 07 19:06:14 2003
[path: D:\Program Files\Debugging Tools for Windows\dbghelp.dll]
ext: image 6.X.0005.0, API 1.0.0, built Fri Mar 07 19:06:05 2003
[path: D:\Program Files\Debugging Tools for Windows\winext\ext.dll]

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"Dominic Hopton" <domini...@hotmail.com> wrote in message

news:e0ZgFtP#CHA....@TK2MSFTNGP12.phx.gbl...

Dominic Hopton

unread,
Apr 2, 2003, 4:04:42 PM4/2/03
to
I do get those messages when I load the image.
I apologise for doing !chain. Busy yada yada :)

The same errors and outputs happen on an SP3 memory dump. The same errors
happen when I make sure the dump is loaded off a local drive.
I've reinstalled WinDBG on both machines where I am seeing this error. I'm
feeling stupid :)

Yours,
Dominic

Here is the output from my session:
--------------

Microsoft (R) Windows Debugger Version 6.1.0017.2


Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [\\lrrr\c$\winnt\MEMORY.DMP]
Kernel Dump File: Full address space is available

Symbol search path is: *** Invalid *** : Verify _NT_SYMBOL_PATH setting
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************


*** ERROR: Symbol file could not be found. Defaulted to export symbols for

ntkrnlmp.exe -
Windows 2000 Kernel Version 2195 (Service Pack 4, RC 4.36) MP (2 procs) Free
x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Kernel base = 0x80400000 PsLoadedModuleList = 0x804841e0
Debug session time: Tue Apr 01 11:43:55 2003
System Uptime: 0 days 7:53:37.250
WARNING: Process directory table base 09785000 doesn't match CR3 00030000
WARNING: Process directory table base 09785000 doesn't match CR3 00030000
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Bugcheck code 0000009C
Arguments 00000002 003446ff b6000000 00140001

ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
8187ba3c 80062be2 80271000 00000000 00000001 0x80062c4c
00000000 00000000 00000000 00000000 00000000 0x80062be2

WaitForEvent failed


0: kd> !analyze
No export analyze found

0: kd> .chain


Default extension DLLs are not loaded until after initial connection

"Ivan Brugiolo [MSFT]" <ivan...@online.microsoft.com> wrote in message

news:OpKPD$S#CHA....@TK2MSFTNGP10.phx.gbl...

David Holcomb [MS]

unread,
Apr 5, 2003, 11:18:35 AM4/5/03
to
Where are you loading windbg from? Can you check the directory to make sure
all the extension subdirectories are present? (e.g. do "dir /s /b" from the
directory where the debugger is installed).

Also try "kd -y SRV*http://msdl.microsoft.com/download/symbols -z
\\lrrr\c$\winnt\MEMORY.DMP". Your symbol path is not set but the debugger
should still load the right extensions because the OS information was
detected.

If kd works, try the same command line with windbg.

--


--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Dominic Hopton" <domini...@hotmail.com> wrote in message

news:OK9z9tV#CHA....@TK2MSFTNGP12.phx.gbl...

0 new messages