Hi, is there anybody who can point me to a article or give an answer to the
simple question why my com port is not working when I boot any of my
machines in /debug mode ? I have no problems adding and configuring a com
port however as soon as I boot in /debug mode the com port is eliminated or
otherwise I receive a message ‘this device cannot start’. I have been
fooling around for days to get this going and experience the same behaviour
on all platforms I have tried so far: Win2003 R2, Win XP Sp2, Win XP home
edition and WinXp x64.
The only thing I got going so far is debugging over a named pipe with
VmWare. Is there any chance local debugging will be added to Windbg in the
future ? I wish SoftIce were still here.
/Daniel
When you add one of the debug options to the boot line in boot.ini and
specify the use of serial, either the default com port or the one you
specify is opened exclusively for the use of the debugging system. Hence,
you cannot then see it from most anything available to the user. If you
can, move to 1394. It’s a much better debug experience.
You can use on of the debugging monitors to view debug spew. Check the
OsrOnline site and I think SysInternals has one as well. I use OSR’s
DbgMon and find it about as easy to use as there is.
Gary G. Little
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Terhell
Sent: Friday, June 23, 2006 7:35 AM
To: Kernel Debugging Interest List
Subject: [windbg] How to configure a COM port in debug mode
Hi, is there anybody who can point me to a article or give an answer to
the
simple question why my com port is not working when I boot any of my
machines in /debug mode ? I have no problems adding and configuring a com
port however as soon as I boot in /debug mode the com port is eliminated
or
otherwise I receive a message ‘this device cannot start’. I have been
fooling around for days to get this going and experience the same
behaviour
on all platforms I have tried so far: Win2003 R2, Win XP Sp2, Win XP home
edition and WinXp x64.
The only thing I got going so far is debugging over a named pipe with
VmWare. Is there any chance local debugging will be added to Windbg in the
future ? I wish SoftIce were still here.
/Daniel
You are currently subscribed to windbg as: xxxxx@seagate.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
And /DEBUG without any other debug control switches implies serial (normally
com2) with a slow baudrate (normally 19200). I say normally, because some
later systems and 64-bit change the defaults.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply
wrote in message news:xxxxx@windbg…
> When you add one of the debug options to the boot line in boot.ini and
> specify the use of serial, either the default com port or the one you
> specify is opened exclusively for the use of the debugging system. Hence,
> you cannot then see it from most anything available to the user. If you
> can, move to 1394. It’s a much better debug experience.
>
> You can use on of the debugging monitors to view debug spew. Check the
> OsrOnline site and I think SysInternals has one as well. I use OSR’s
> DbgMon and find it about as easy to use as there is.
>
> Gary G. Little
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Terhell
> Sent: Friday, June 23, 2006 7:35 AM
> To: Kernel Debugging Interest List
> Subject: [windbg] How to configure a COM port in debug mode
>
> Hi, is there anybody who can point me to a article or give an answer to
> the
> simple question why my com port is not working when I boot any of my
> machines in /debug mode ? I have no problems adding and configuring a com
>
> port however as soon as I boot in /debug mode the com port is eliminated
> or
> otherwise I receive a message ‘this device cannot start’. I have been
> fooling around for days to get this going and experience the same
> behaviour
> on all platforms I have tried so far: Win2003 R2, Win XP Sp2, Win XP home
> edition and WinXp x64.
>
> The only thing I got going so far is debugging over a named pipe with
> VmWare. Is there any chance local debugging will be added to Windbg in the
>
> future ? I wish SoftIce were still here.
>
> /Daniel
>
>
>
> —
> You are currently subscribed to windbg as: xxxxx@seagate.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
Thanks, until now I had been so naive to expect a working com port displayed
in the device manager. It gives me encouragement to try on.
/Daniel
wrote in message news:xxxxx@windbg…
> When you add one of the debug options to the boot line in boot.ini and
> specify the use of serial, either the default com port or the one you
> specify is opened exclusively for the use of the debugging system. Hence,
> you cannot then see it from most anything available to the user. If you
> can, move to 1394. It’s a much better debug experience.
>
> You can use on of the debugging monitors to view debug spew. Check the
> OsrOnline site and I think SysInternals has one as well. I use OSR’s
> DbgMon and find it about as easy to use as there is.
>
> Gary G. Little
>
When you use a com port for debugging, it is only available then for
debugging. You cannot use it for any other purpose than to connect a
second PC to it that is running windbg. It is always removed from device
manager when it is specified as a debugport in boot.ini since it is
reserved exclusively for debug use at that point. You should only set
that flag in the target computer, not on the one that is running windbg.
Beverly
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Terhell
Sent: Friday, June 23, 2006 8:35 AM
To: Kernel Debugging Interest List
Subject: [windbg] How to configure a COM port in debug mode
Hi, is there anybody who can point me to a article or give an answer to
the simple question why my com port is not working when I boot any of my
machines in /debug mode ? I have no problems adding and configuring a
com port however as soon as I boot in /debug mode the com port is
eliminated or otherwise I receive a message ‘this device cannot start’.
I have been fooling around for days to get this going and experience the
same behaviour on all platforms I have tried so far: Win2003 R2, Win XP
Sp2, Win XP home edition and WinXp x64.
The only thing I got going so far is debugging over a named pipe with
VmWare. Is there any chance local debugging will be added to Windbg in
the future ? I wish SoftIce were still here.
/Daniel
You are currently subscribed to windbg as: bbrown@mc.com To unsubscribe
send a blank email to xxxxx@lists.osr.com
You can also read
http://blogs.msdn.com/doronh/archive/2006/06/07/621604.aspx for more
info on this
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Terhell
Sent: Friday, June 23, 2006 7:27 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] How to configure a COM port in debug mode
Thanks, until now I had been so naive to expect a working com port
displayed in the device manager. It gives me encouragement to try on.
/Daniel
wrote in message news:xxxxx@windbg…
> When you add one of the debug options to the boot line in boot.ini and
> specify the use of serial, either the default com port or the one you
> specify is opened exclusively for the use of the debugging system.
> Hence, you cannot then see it from most anything available to the
> user. If you can, move to 1394. It’s a much better debug experience.
>
> You can use on of the debugging monitors to view debug spew. Check the
> OsrOnline site and I think SysInternals has one as well. I use OSR’s
> DbgMon and find it about as easy to use as there is.
>
> Gary G. Little
>
—
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com