I haven’t dug into this very far, but I’ve seen this problems on some
machines that I have here and yet on others WinDBG works fine across
reboots of the target machine. It’s really weird (and frustrating) when it
works on one machine but not on another… is it possible that the problem
is with the hal? The only reason I mention this is that on the machine here
that works fine, we use the non-ACPI hal (hal.dll) but on the 2 where the
reboot fails if WinDBG is connected, they are both ACPI machines… I know
this could be quite a stretch, but it’s the only real difference I’ve found
so far in the configurations of the machines… I am seeing this behavior
with the latest version (3.0.0020.0) of windbg…
The machines that lock show the following characteristics:
- If WinDBG is connected and the machines reboot (I use the /sos switch in
boot.ini), the machine that is booting will lock right after it gets done
displaying the initial listing of drivers that are loading… It never
moves on to the next screen that displays ‘Windows 2000’ at the top and
shows the output of the disk checks, etc. I would assume this is when
WinDBG actually connects since it is the first time that you see the
“System Uptime” and “Kernel Base =” error messages… - The host system that is running WinDBG will not be able to break into the
machine, etc, and will just sit there after getting the initial debug
messages of “Kernel Base =” and “System Uptime”…
Has anyone successfully used WinDBG across reboots on an ACPI-hal machine?
Is there anything different between the ACPI hal and the non-ACPI hal that
would affect WinDBG or the com port handling on the target machine? To
check the version of the HAL you are using, look in
c:\winnt\repair\setup.log and look for the line that has “hal.dll” in it…
if you see the following line:
\WINNT\system32\hal.dll = “halacpi.dll”,“1e136”
then you are using the ACPI hal…
I have not tested WinXP debugging on an ACPI-enabled machine…
Just my stab in the dark… hope something in this email helps…
sean
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com