Dear All,
Each time after I reboot the target machine… running (release W2K with
checked ntoskrnl and hal ) my windbg is unable to automatically connect to
the target machine. I have to kill windbg and re-run it in order to start
debugging. But then I miss part when driver is being loaded ( which right
now is a problem with my driver that I want to debug ).
Is it not possible for windbg to connect when the target system is
rebooting ? If its not possible, then how do people debug when a driver
loads perfectly well after ‘add/remove new hardware’ sequence but fails to
load automatically after system reboot ? In fact my W2K fails to reboot
because of my driver.
thanks for any help…
regards,
Hassan
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
Which version of WinDbg are you using? You should be using 3.00.0010.
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com
-----Original Message-----
From: xxxxx@hotmail.com [mailto:xxxxx@hotmail.com]
Sent: Wednesday, July 25, 2001 6:41 AM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg does not connect after target reboots
Dear All,
Each time after I reboot the target machine… running (release W2K with
checked ntoskrnl and hal ) my windbg is unable to automatically connect to
the target machine. I have to kill windbg and re-run it in order to start
debugging. But then I miss part when driver is being loaded ( which right
now is a problem with my driver that I want to debug ).
Is it not possible for windbg to connect when the target system is
rebooting ? If its not possible, then how do people debug when a driver
loads perfectly well after ‘add/remove new hardware’ sequence but fails to
load automatically after system reboot ? In fact my W2K fails to reboot
because of my driver.
thanks for any help…
regards,
Hassan
You are currently subscribed to windbg as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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
Hmm, not sure what’s going wrong for you, so I’ll give the cookbook version.
- Your WindBag should be 3.0.0010.0, if it isn’t, get the latest 'Bag from
http://www.microsoft.com/ddk/debugging/
- Start the 'Bag on your debugger host.
- Set up the kernel connection.
3a. If you need to instantiate breakpoints, toggle the “initial
breakpoint” with Ctrl+Alt+K.
- Start the target.
- Select the “debugger enabled” configuration from the menu. If you don’t
have this, then you haven’t prepared your target properly. The 'Bag docs
will tell you how to do this.
- If you’ve set everything up properly, your debugging setup should enable
you to debug your driver.
Phil
-----Original Message-----
From: xxxxx@hotmail.com [mailto:xxxxx@hotmail.com]
Sent: Wednesday, July 25, 2001 6:41 AM
To: Kernel Debugging Interest List
Subject: [windbg] Windbg does not connect after target reboots
Dear All,
Each time after I reboot the target machine… running (release W2K with
checked ntoskrnl and hal ) my windbg is unable to automatically connect to
the target machine. I have to kill windbg and re-run it in order to start
debugging. But then I miss part when driver is being loaded ( which right
now is a problem with my driver that I want to debug ).
Is it not possible for windbg to connect when the target system is
rebooting ? If its not possible, then how do people debug when a driver
loads perfectly well after ‘add/remove new hardware’ sequence but fails to
load automatically after system reboot ? In fact my W2K fails to reboot
because of my driver.
thanks for any help…
regards,
Hassan
You are currently subscribed to windbg as: xxxxx@intel.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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
Yes, I am using 3.00.0010.
==================== windbg session dump ==================
Opened \.\com1
Microsoft (R) Windows Kernel Debugger
Version 3.0.0010.0
Copyright (c) Microsoft Corporation. All rights reserved.
Waiting to reconnect…
Will request initial breakpoint at next boot.
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established. (Initial Breakpoint requested)
Loaded dbghelp extension DLL
Loaded ext extension DLL
Loaded kext extension DLL
Loaded kdextx86 extension DLL
Symbol search path is: c:\win2kdat\retailsymbols2k
Symbol search path is: c:\win2kdat\retailsymbols2k
Executable search path is: d:\winnt\system32\drivers
PsLoadedModuleList not initialized yet. Delay kernel load.
Windows 2000 Kernel Version 2195 UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618
System Uptime: not available
==================== windbg session dump end ================
This is where it just remain hung. Ctrl+Brk doesn’t work here and ‘go’
button and others are greyed out.
regards,
Hassan
From: Gary Little
>Reply-To: “Kernel Debugging Interest List”
>To: “Kernel Debugging Interest List”
>Subject: [windbg] RE: Windbg does not connect after target reboots
>Date: Wed, 25 Jul 2001 11:01:42 -0700
>
>Which version of WinDbg are you using? You should be using 3.00.0010.
>
>Gary G. Little
>Staff Engineer
>Broadband Storage, Inc.
>xxxxx@broadstor.com
>
>-----Original Message-----
>From: xxxxx@hotmail.com [mailto:xxxxx@hotmail.com]
>Sent: Wednesday, July 25, 2001 6:41 AM
>To: Kernel Debugging Interest List
>Subject: [windbg] Windbg does not connect after target reboots
>
>Dear All,
>
>Each time after I reboot the target machine… running (release W2K with
>checked ntoskrnl and hal ) my windbg is unable to automatically connect to
>the target machine. I have to kill windbg and re-run it in order to start
>debugging. But then I miss part when driver is being loaded ( which right
>now is a problem with my driver that I want to debug ).
>
>Is it not possible for windbg to connect when the target system is
>rebooting ? If its not possible, then how do people debug when a driver
>loads perfectly well after ‘add/remove new hardware’ sequence but fails to
>load automatically after system reboot ? In fact my W2K fails to reboot
>because of my driver.
>
>thanks for any help…
>regards,
>Hassan
>
>—
>You are currently subscribed to windbg as: xxxxx@broadstor.com
>To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>—
>You are currently subscribed to windbg as: xxxxx@hotmail.com
>To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
—
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
I’ve never seen this problem, so the following is speculation. You say you
are running the checked build HAL and kernel, is it possible it’s a symbol
mis-match issue? Are the serial ports set to the same speed? Is the
problem the same if you slow it down to 19,200?
-----Original Message-----
From: Hassan I Khan [mailto:xxxxx@hotmail.com]
Sent: Wednesday, July 25, 2001 1:14 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Windbg does not connect after target reboots
Yes, I am using 3.00.0010.
==================== windbg session dump ==================
Opened \.\com1
Microsoft (R) Windows Kernel Debugger
Version 3.0.0010.0
Copyright (c) Microsoft Corporation. All rights reserved.
Waiting to reconnect…
Will request initial breakpoint at next boot.
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established. (Initial Breakpoint requested)
Loaded dbghelp extension DLL
Loaded ext extension DLL
Loaded kext extension DLL
Loaded kdextx86 extension DLL
Symbol search path is: c:\win2kdat\retailsymbols2k
Symbol search path is: c:\win2kdat\retailsymbols2k
Executable search path is: d:\winnt\system32\drivers
PsLoadedModuleList not initialized yet. Delay kernel load.
Windows 2000 Kernel Version 2195 UP Free x86 compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618
System Uptime: not available
==================== windbg session dump end ================
This is where it just remain hung. Ctrl+Brk doesn’t work here and ‘go’
button and others are greyed out.
regards,
Hassan
From: Gary Little
>Reply-To: “Kernel Debugging Interest List”
>To: “Kernel Debugging Interest List”
>Subject: [windbg] RE: Windbg does not connect after target reboots
>Date: Wed, 25 Jul 2001 11:01:42 -0700
>
>Which version of WinDbg are you using? You should be using 3.00.0010.
>
>Gary G. Little
>Staff Engineer
>Broadband Storage, Inc.
>xxxxx@broadstor.com
>
>-----Original Message-----
>From: xxxxx@hotmail.com [mailto:xxxxx@hotmail.com]
>Sent: Wednesday, July 25, 2001 6:41 AM
>To: Kernel Debugging Interest List
>Subject: [windbg] Windbg does not connect after target reboots
>
>Dear All,
>
>Each time after I reboot the target machine… running (release W2K with
>checked ntoskrnl and hal ) my windbg is unable to automatically connect to
>the target machine. I have to kill windbg and re-run it in order to start
>debugging. But then I miss part when driver is being loaded ( which right
>now is a problem with my driver that I want to debug ).
>
>Is it not possible for windbg to connect when the target system is
>rebooting ? If its not possible, then how do people debug when a driver
>loads perfectly well after ‘add/remove new hardware’ sequence but fails to
>load automatically after system reboot ? In fact my W2K fails to reboot
>because of my driver.
>
>thanks for any help…
>regards,
>Hassan
>
>—
>You are currently subscribed to windbg as: xxxxx@broadstor.com
>To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>—
>You are currently subscribed to windbg as: xxxxx@hotmail.com
>To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
—
You are currently subscribed to windbg as: xxxxx@intel.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
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
Thanks Phil your speculations turned out to be useful. It started working
when I lowered the speed to 19200 (from 38400). Using the matching symbols
however didn’t improve anything.
regards,
Hassan
From: “Barila, Phil”
>Reply-To: “Kernel Debugging Interest List”
>To: “Kernel Debugging Interest List”
>Subject: [windbg] RE: Windbg does not connect after target reboots
>Date: Wed, 25 Jul 2001 13:42:21 -0700
>
>I’ve never seen this problem, so the following is speculation. You say you
>are running the checked build HAL and kernel, is it possible it’s a symbol
>mis-match issue? Are the serial ports set to the same speed? Is the
>problem the same if you slow it down to 19,200?
>
>-----Original Message-----
>From: Hassan I Khan [mailto:xxxxx@hotmail.com]
>Sent: Wednesday, July 25, 2001 1:14 PM
>To: Kernel Debugging Interest List
>Subject: [windbg] RE: Windbg does not connect after target reboots
>
>
>Yes, I am using 3.00.0010.
>
>==================== windbg session dump ==================
>Opened \.\com1
>
>Microsoft (R) Windows Kernel Debugger
>Version 3.0.0010.0
>Copyright (c) Microsoft Corporation. All rights reserved.
>
>Waiting to reconnect…
>Will request initial breakpoint at next boot.
>Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
>Kernel Debugger connection established. (Initial Breakpoint requested)
>Loaded dbghelp extension DLL
>Loaded ext extension DLL
>Loaded kext extension DLL
>Loaded kdextx86 extension DLL
>Symbol search path is: c:\win2kdat\retailsymbols2k
>Symbol search path is: c:\win2kdat\retailsymbols2k
>Executable search path is: d:\winnt\system32\drivers
>PsLoadedModuleList not initialized yet. Delay kernel load.
>Windows 2000 Kernel Version 2195 UP Free x86 compatible
>Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618
>System Uptime: not available
>
>==================== windbg session dump end ================
>
>This is where it just remain hung. Ctrl+Brk doesn’t work here and ‘go’
>button and others are greyed out.
>
>regards,
>Hassan
>
>
> >From: Gary Little
> >Reply-To: “Kernel Debugging Interest List”
> >To: “Kernel Debugging Interest List”
> >Subject: [windbg] RE: Windbg does not connect after target reboots
> >Date: Wed, 25 Jul 2001 11:01:42 -0700
> >
> >Which version of WinDbg are you using? You should be using 3.00.0010.
> >
> >Gary G. Little
> >Staff Engineer
> >Broadband Storage, Inc.
> >xxxxx@broadstor.com
> >
> >-----Original Message-----
> >From: xxxxx@hotmail.com [mailto:xxxxx@hotmail.com]
> >Sent: Wednesday, July 25, 2001 6:41 AM
> >To: Kernel Debugging Interest List
> >Subject: [windbg] Windbg does not connect after target reboots
> >
> >Dear All,
> >
> >Each time after I reboot the target machine… running (release W2K with
> >checked ntoskrnl and hal ) my windbg is unable to automatically connect
>to
> >the target machine. I have to kill windbg and re-run it in order to start
> >debugging. But then I miss part when driver is being loaded ( which right
> >now is a problem with my driver that I want to debug ).
> >
> >Is it not possible for windbg to connect when the target system is
> >rebooting ? If its not possible, then how do people debug when a driver
> >loads perfectly well after ‘add/remove new hardware’ sequence but fails
>to
> >load automatically after system reboot ? In fact my W2K fails to reboot
> >because of my driver.
> >
> >thanks for any help…
> >regards,
> >Hassan
> >
> >—
> >You are currently subscribed to windbg as: xxxxx@broadstor.com
> >To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> >—
> >You are currently subscribed to windbg as: xxxxx@hotmail.com
> >To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
>
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>
>—
>You are currently subscribed to windbg as: xxxxx@intel.com
>To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
>—
>You are currently subscribed to windbg as: xxxxx@hotmail.com
>To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
—
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
You might try a different cable. Only being able to drive it at 19,200
seems pretty low. I know this is an obvious question, but before you
changed the speed, was it the same at both ends?
-----Original Message-----
From: Hassan I Khan [mailto:xxxxx@hotmail.com]
Sent: Wednesday, July 25, 2001 5:17 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Windbg does not connect after target reboots
Thanks Phil your speculations turned out to be useful. It started working
when I lowered the speed to 19200 (from 38400). Using the matching symbols
however didn’t improve anything.
regards,
Hassan
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
Yes, it was. I will try a different cable but I know it works fine on 38400
when windows is fully booted up. Its only during the reboot that I was
experiencing this problem.
regards,
Hassan
From: “Barila, Phil”
>Reply-To: “Kernel Debugging Interest List”
>To: “Kernel Debugging Interest List”
>Subject: [windbg] RE: Windbg does not connect after target reboots
>Date: Wed, 25 Jul 2001 17:28:02 -0700
>
>You might try a different cable. Only being able to drive it at 19,200
>seems pretty low. I know this is an obvious question, but before you
>changed the speed, was it the same at both ends?
>
>-----Original Message-----
>From: Hassan I Khan [mailto:xxxxx@hotmail.com]
>Sent: Wednesday, July 25, 2001 5:17 PM
>To: Kernel Debugging Interest List
>Subject: [windbg] RE: Windbg does not connect after target reboots
>
>
>Thanks Phil your speculations turned out to be useful. It started working
>when I lowered the speed to 19200 (from 38400). Using the matching symbols
>however didn’t improve anything.
>
>regards,
>Hassan
>
>
>—
>You are currently subscribed to windbg as: xxxxx@hotmail.com
>To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
—
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
It has been my experience that some COM ports just have some kind of problem with a certian speed. Sometimes changing the speed to lower or higher speed will resolve the issue. Sometimes changing what ports you connect to (both the host and debugge side) will resolve the issue.
There doesn’t seem to be any rhyme or reason to it. Different hardware from different vendors seem equally affected. No one baudrate seems immune. I’ve seen ports that work well only at lower speeds and I’ve seem some that work well on higher speeds. I’ve even seen one that worked on any speed but 57600.
Make sure to try the whole range. I personally try to run at 115200 which is the fastest com ports can go.
-----Original Message-----
From: Hassan I Khan [mailto:xxxxx@hotmail.com]
Sent: Wed 7/25/2001 6:23 PM
To: Kernel Debugging Interest List
Cc:
Subject: [windbg] RE: Windbg does not connect after target reboots
Yes, it was. I will try a different cable but I know it works fine on 38400
when windows is fully booted up. Its only during the reboot that I was
experiencing this problem.
regards,
Hassan
From: “Barila, Phil”
>Reply-To: “Kernel Debugging Interest List”
>To: “Kernel Debugging Interest List”
>Subject: [windbg] RE: Windbg does not connect after target reboots
>Date: Wed, 25 Jul 2001 17:28:02 -0700
>
>You might try a different cable. Only being able to drive it at 19,200
>seems pretty low. I know this is an obvious question, but before you
>changed the speed, was it the same at both ends?
>
>-----Original Message-----
>From: Hassan I Khan [mailto:xxxxx@hotmail.com]
>Sent: Wednesday, July 25, 2001 5:17 PM
>To: Kernel Debugging Interest List
>Subject: [windbg] RE: Windbg does not connect after target reboots
>
>
>Thanks Phil your speculations turned out to be useful. It started working
>when I lowered the speed to 19200 (from 38400). Using the matching symbols
>however didn’t improve anything.
>
>regards,
>Hassan
>
>
>—
>You are currently subscribed to windbg as: xxxxx@hotmail.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
—
You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
b???.???????&?v?0?w[??,??-E?“?I??Pv???{.n?+???zwZnV??隊[h???{?u?,??-E?”?Ǧm??(Z?X???,??&
For what it is worth, I have complained about this before myself. About 1/2
the time the system gets hung up at the same point. I type -r,
it works sometimes, or at least it seems to work. I’m running the checked
build of XP RC1, at 57600. I did have trouble going faster.
My solution is to boot the system as infrequently as possible. I
dynamically reload new copies of my driver using the control panel. If I do
get a crash, I cross my fingers and know I’ll probably have to reset the
target machine a couple of times before I get a good debugger connection.
I’m using a good cable. I’m using the latest WinDBG. I think the bottom
line is something is broken with WinDBG. I just can’t prove it, but at
least you and I both know we are not alone.
-Evan
>
> Waiting to reconnect…
> Will request initial breakpoint at next boot.
> Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established. (Initial Breakpoint requested)
> Loaded dbghelp extension DLL
> Loaded ext extension DLL
> Loaded kext extension DLL
> Loaded kdextx86 extension DLL
> Symbol search path is: c:\win2kdat\retailsymbols2k
> Symbol search path is: c:\win2kdat\retailsymbols2k
> Executable search path is: d:\winnt\system32\drivers
> PsLoadedModuleList not initialized yet. Delay kernel load.
> Windows 2000 Kernel Version 2195 UP Free x86 compatible
> Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618
> System Uptime: not available
>
—
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
I have run across this but I simply restart the debugger before I select the
OS to boot. It is always fine, no crossing of the fingers and only resetting
once … I don’t really find this to be an issue at all.
Pete
Peter Scott
xxxxx@KernelDrivers.com
http://www.KernelDrivers.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
Sent: Thursday, July 26, 2001 8:30 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Windbg does not connect after target reboots
For what it is worth, I have complained about this before myself. About 1/2
the time the system gets hung up at the same point. I type -r,
it works sometimes, or at least it seems to work. I’m running the checked
build of XP RC1, at 57600. I did have trouble going faster.
My solution is to boot the system as infrequently as possible. I
dynamically reload new copies of my driver using the control panel. If I do
get a crash, I cross my fingers and know I’ll probably have to reset the
target machine a couple of times before I get a good debugger connection.
I’m using a good cable. I’m using the latest WinDBG. I think the bottom
line is something is broken with WinDBG. I just can’t prove it, but at
least you and I both know we are not alone.
-Evan
>
> Waiting to reconnect…
> Will request initial breakpoint at next boot.
> Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE
> Kernel Debugger connection established. (Initial Breakpoint requested)
> Loaded dbghelp extension DLL
> Loaded ext extension DLL
> Loaded kext extension DLL
> Loaded kdextx86 extension DLL
> Symbol search path is: c:\win2kdat\retailsymbols2k
> Symbol search path is: c:\win2kdat\retailsymbols2k
> Executable search path is: d:\winnt\system32\drivers
> PsLoadedModuleList not initialized yet. Delay kernel load.
> Windows 2000 Kernel Version 2195 UP Free x86 compatible
> Kernel base = 0x80400000 PsLoadedModuleList = 0x8046b618
> System Uptime: not available
>
—
You are currently subscribed to windbg as: xxxxx@home.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
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
Pete,
I have learned to live with it, too. But that does not mean WinDBG is not
broken. How can the WinDBG developers know to fix something like this if we
quietly work around problems? The WinDBG developers are pretty committed to
a solid product. If it becomes clear this is not an odd user error, they
will prioritize it.
That make three of us so far - anyone else seen this?
-Evan
I have run across this but I simply restart the debugger before I
select the
OS to boot. It is always fine, no crossing of the fingers and
only resetting
once … I don’t really find this to be an issue at all.
Pete
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
All,
FWIW, I have seen it too. I, too considered it a minor problem, and “worked
around it”.
Bill Christie, Software Engineer
Link Engineering Company
43855 Plymouth Oaks Blvd.
Plymouth, MI 48170
www.linkeng.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Evan Hillman
Sent: Thursday, July 26, 2001 2:36 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Windbg does not connect after target reboots
Pete,
I have learned to live with it, too. But that does not mean
WinDBG is not
broken. How can the WinDBG developers know to fix something
like this if we
quietly work around problems? The WinDBG developers are
pretty committed to
a solid product. If it becomes clear this is not an odd user
error, they
will prioritize it.
That make three of us so far - anyone else seen this?
-Evan
>
> I have run across this but I simply restart the debugger before I
> select the
> OS to boot. It is always fine, no crossing of the fingers and
> only resetting
> once … I don’t really find this to be an issue at all.
>
> Pete
>
>
You are currently subscribed to windbg as: xxxxx@linkeng.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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