trouble with WinDBG and Windows 2000 RC2
Jason Lin
Does any one know how to get two x86 Windows 2000 RC2 free build
connected via WinDbg 5.00.2022.1 ? The connection is good, I verify it
with two hyperterminal connect with each other. When the target starts,
the host just waiting for connection and does not know the target is
up. I also specify "Enable Kernel Debug, go on exit" on windbg. I try
to break into the targe machine with CTRL+C, windbg shows that it is
processing stopping. I try to issue !reload or some other commands,
Windbg says that can't execute the command when target machine is
running. But actually the target machine is frozen due to the CTRL+C
request ! After that, I can't make the target machine re-run unless I
reboot the machine. :-(.
I check microsoft's web site and download the post RC1 Windbg but
also does not work for me. Must the target machine be checked build ?
Any information is appreciated.
--
Jason Lin
Sent via Deja.com http://www.deja.com/
Before you buy.
David Schwartz
- It is no longer possible to use <Control/C> or the break button to break
into the debugger. Windbg ignores the command.
- Single stepping from a breakpoint causes the debugger to crash. Its not a
Dr. Watson error, the debugger simply disappears without a trace. No popup
messages or anything!
- Symbol resolution for global symbols (extern) does not work unless you are
currently running the driver that declares the symbol. You can open a watch
window using the "driverName!Symbol" syntax, but when you click on the + sign
to expand the structure all you see is a bunch of garbage (boxes, control
characters, etc). If you reset EIP to point to a routine within the driver
(say DriverEntry), the symbol is resolved and displayed just fine.
I opened a bug report with Microsoft on this (case number: SRX991022600850).
Attached are the responses from Microsoft support. I have it on good authority
that the kernel development group at Microsoft uses i386kd.exe
I rolled back to the Sept. 1998 Platform SDK and have had much better
luck with windbg.
David Schwartz
--------------------------------------------------------------------------------
-----Original Message-----
From: Guru Huchurao [mailto:gh...@microsoft.com]
Sent: Monday, October 25, 1999 2:37 PM
To: 'David Schwartz'
Subject: RE: SRX991022600850.
Hello David,
I understand that customers are facing problems with WinDbg. The bugs which
you have specified and experienced is known and we are working on it.
I am considering this case as Nondecremental and the case is not charged. I
will be happy to provide the best support that I can.
Once again I apologise for this issue.
Meanwhile I am also trying to find out any alternatives that can be used. I
will keep in touch with you.
With Best Regards,
Huchu Rao Gurupurna
-----Original Message-----
From: Guru Huchurao [mailto:gh...@microsoft.com]
Sent: Monday, October 25, 1999 7:15 PM
To: 'David Schwartz'
Subject: RE: SRX991022600850.
Hello David,
As I told you earlier that we understand that there has been problems in
windbg. This is because we are adding new features such as 64 bit debugging
and other new set of features because of which the windbg has problems, we
are also very much interested in the feed back with respect to debuggers
such as yours. This will help us in improving the quality of the product.
Also we understand that debugging the kernel level stuff is very difficult
and hence our priority and goad is to give the highest support both interms
of tools as well as technological support. But as you know a good software
will evolve with respect to time. So As I told earlier we have informed the
people who are responsible for the debuggers and you can expect a good
debugging tools from MS soon. Also if you are familier with assembly
language, I would suggest u to use Kernel debugger i386kd.exe which is most
efficient and stable debugger.
I appreciate your feed back and frank opinion which helps us in providing a
good debugging support.
Please let me know whether I can close this case, as we know there is a
problem in the debugger. I would close this case as nondecremental and your
money will be credited back.
With Warm Regards,
Huchu Rao Gurupurna
TEL - (425) 704-2050
Windows NT DDK Support
http://support.microsoft.com/support/ddk/ntddk
Microsoft Technical Support http://support.microsoft.com/support
Hardware Technologies Unit http://www.microsoft.com/hwdev
We want to ensure you are fully satisfied with the level of support we
provide. If you have any concerns, or would like to share feedback
surrounding your experience, please contact my manager Kevin Turner at
[<mailto:ktu...@microsoft.com>].