The latest Windbg allows debugging over a network connection (File->Kernel
Debug) but there seems to be no documentation about it. Does anyone know how
to setup a target system so that it can be debugged over a network ? In the
bcdedit help I only see the options SERIAL, 1394 and USB listed. Thanks.
//Daniel
Bryce gave the answer over in the MS groups:
Apprently just mistakenly left in the public build. Hopefully we’ll see the
support in the future.
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
wrote in message news:xxxxx@windbg…
> The latest Windbg allows debugging over a network connection (File->Kernel
> Debug) but there seems to be no documentation about it. Does anyone know
> how to setup a target system so that it can be debugged over a network ?
> In the bcdedit help I only see the options SERIAL, 1394 and USB listed.
> Thanks.
>
> //Daniel
>
Nice article on remote debugging here:
http://blogs.msdn.com/ntdebugging/archive/2009/02/09/remote-debugging-connecting-to-a-remote-stub-using-the-microsoft-debugging-tools-for-windows.aspx
Chandra
On Wed, Jun 17, 2009 at 7:13 AM, Scott Noone wrote:
> Bryce gave the answer over in the MS groups:
>
> http://tinyurl.com/kry8qw
>
> Apprently just mistakenly left in the public build. Hopefully we’ll see the
> support in the future.
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> wrote in message news:xxxxx@windbg…
> > The latest Windbg allows debugging over a network connection
> (File->Kernel
> > Debug) but there seems to be no documentation about it. Does anyone know
> > how to setup a target system so that it can be debugged over a network ?
> > In the bcdedit help I only see the options SERIAL, 1394 and USB listed.
> > Thanks.
> >
> > //Daniel
> >
>
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
That article is totally different than the what is being referred to in this
thread. That has been present since 2002, what is being asked is a
replacement for 1394 or serial using Ethernet.
–
Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“chandra97 97” wrote in message news:xxxxx@windbg…
> Nice article @ÏüPÑ0Íemote debugging here:
> http://blogs.msdn.com/ntdebugging/archive/2009/02/09/remote-debugging-connecting-to-a-remote-stub-using-the-microsoft-debugging-tools-for-windows.aspx
>
> Chandra
>
>
> On Wed, Jun 17, 2009 at 7:13 AM, Scott Noone wrote:
>
>> Bryce gave the answer over in the MS groups:
>>
>> http://tinyurl.com/kry8qw
>>
>> Apprently just mistakenly left in the public build. Hopefully we’ll see
>> the
>> support in the future.
>>
>> -scott
>>
>> –
>> Scott Noone
>> Consulting AssociatPÑüÓ@Ï OSR Open Systems Resources, Inc.<br>>> http://www.osronline.com<br>>><br>>><br>>> <xxxxx> wrote in message news:xxxxx@windbg...<br>>> > The latest Windbg allows debugging over a network connection<br>>> (File->Kernel<br>>> > Debug) but there seems to be no documentation about it. Does anyone <br>>> > know<br>>> > how to setup a target system so that it can be debugged over a network <br>>> > ?<br>>> > In the bcdedit help I only see the options SERIAL, 1394 and USB listed.<br>>> > Thanks.<br>>> ><br>>> > //Daniel<br>>> ><br>>><br>>><br>>><br>>> ---<br>>> WÓüpÕPÑG is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4163 (20090617)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
Information from ESET NOD32 Antivirus, version of virus signature database 4163 (20090617)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
> That article is totally different than the what is being referred to in
this
thread. hat has been present since 2002
The timestamp towards title is “Monday, February 09, 2009 2:20 PM”. What I
understood is OP is asking about debugging a remote machine over the
network.
On Wed, Jun 17, 2009 at 1:35 PM, Don Burn wrote:
> That article is totally different than the what is being referred to in
> this
> thread. That has been present since 2002, what is being asked is a
> replacement for 1394 or serial using Ethernet.
>
> –
> Don Burn (MVP, Windows DDK)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
> “chandra97 97” wrote in message news:xxxxx@windbg…
> > Nice article @ﾏ � Pﾑ 0ﾍ emote debugging here:
> >
> http://blogs.msdn.com/ntdebugging/archive/2009/02/09/remote-debugging-connecting-to-a-remote-stub-using-the-microsoft-debugging-tools-for-windows.aspx
> >
> > Chandra
> >
> >
> > On Wed, Jun 17, 2009 at 7:13 AM, Scott Noone wrote:
> >
> >> Bryce gave the answer over in the MS groups:
> >>
> >> http://tinyurl.com/kry8qw
> >>
> >> Apprently just mistakenly left in the public build. Hopefully we’ll see
> >> the
> >> support in the future.
> >>
> >> -scott
> >>
> >> –
> >> Scott Noone
> >> Consulting AssociatPﾑ � ﾓ @ﾏ OSR Open Systems Resources, Inc.<br>> >> http://www.osronline.com<br>> >><br>> >><br>> >> <xxxxx> wrote in message news:xxxxx@windbg...<br>> >> > The latest Windbg allows debugging over a network connection<br>> >> (File->Kernel<br>> >> > Debug) but there seems to be no documentation about it. Does anyone<br>> >> > know<br>> >> > how to setup a target system so that it can be debugged over a network<br>> >> > ?<br>> >> > In the bcdedit help I only see the options SERIAL, 1394 and USB<br>> listed.<br>> >> > Thanks.<br>> >> ><br>> >> > //Daniel<br>> >> ><br>> >><br>> >><br>> >><br>> >> ---<br>> >> Wﾓ � pﾕ Pﾑ G is sponsored by OSR
> >>
> >> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> http://www.osr.com/seminars
> >>
> >> To unsubscribe, visit the List Server section of OSR Online at
> >> http://www.osronline.com/page.cfm?name=ListServer
> >>
> >
> >
> >
> > Information from ESET NOD32 Antivirus, version of virus
> > signature database 4163 (20090617)
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4163 (20090617)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
hi,
If you are trying to debug over the network, what you do is to install windbg on the client you want to debug. Start windbg. Open kernel debug for localhost.
on the kd prompt you type
.server tcp:port = 9000
then on the remote pc where you want to debug from, open your debugger and click file and open remote session.
On the window which pops up type the following
tcp:Port=9000,Server=servername
servername is the name of the machine you want to debug. port number can be replaced by whetever port number you want to use which is unsused
Hope this helps
Thanks but this allows only access to a local kernel debugging session which
means you cannot set breakpoints and much.
//Daniel
wrote in message news:xxxxx@windbg…
> hi,
> If you are trying to debug over the network, what you do is to install
> windbg on the client you want to debug. Start windbg. Open kernel debug
> for localhost.
> on the kd prompt you type
>
> .server tcp:port = 9000
>
> then on the remote pc where you want to debug from, open your debugger and
> click file and open remote session.
> On the window which pops up type the following
>
> tcp:Port=9000,Server=servername
>
> servername is the name of the machine you want to debug. port number can
> be replaced by whetever port number you want to use which is unsused
>
> Hope this helps
>
“chandra97 97” wrote in message news:xxxxx@windbg…
>The timestamp towards title is “Monday, February 09, 2009 2:20 PM”. What I
>understood is OP is asking >about debugging a remote machine over the
>network.
While the article is welcome, it involves an extra computer system which is
pre setup. The same could be achieved by using a remote desktop connection.
Meanwhile the actual kernel debugging connection is still over a serial
cable or firewire. In absence of a fully functional local kernel debugger,
remote kernel debugging over a network will reduce the pain by giving great
flexibility.
//Daniel
Hi, guys!
I have noticed the net table in the ‘kernel debugging’ page too. Today I tried to make it work, but failed. I select the net table and input a port number to it and then click OK, it will build a host client. Then I click the ‘break’ button in the menu, it displays that:
Wrote 0 of 1 bytes of the breakin packet.
Failed to write breakin packet to target. Win32 error 0n87
WARNING: The HOST cannot communicate with the TARGET!
But I don’t know how or where I can build a target.
In other computer, I tried to use command “dbgsrv -t tcp:port=9000” to create a debug server(which has a tcp port). But it doesn’t work.
I also tried to use command “.server tcp:port=9000” to establish a network connection. Doesn’t work all the same.
Does anyone konws this? Very thanks!
2009-06-19
“chandra97 97” wrote in message news:xxxxx@windbg…
>The timestamp towards title is “Monday, February 09, 2009 2:20 PM”. What I
>understood is OP is asking >about debugging a remote machine over the
>network.
While the article is welcome, it involves an extra computer system which is
pre setup. The same could be achieved by using a remote desktop connection.
Meanwhile the actual kernel debugging connection is still over a serial
cable or firewire. In absence of a fully functional local kernel debugger,
remote kernel debugging over a network will reduce the pain by giving great
flexibility.
//Daniel
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Go back and look at the link Scott provided. This is an in house stuff that
an interface leaked out.
–
Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“changpei1982” wrote in message
news:xxxxx@windbg…
>
> Hi, guys!
> I have noticed the net table in the ‘kernel debugging’ page too. Today I
> tried to make it work, but failed. I select the net table and input a
> port number to it and then click OK, it will build a host client. Then I
> click the ‘break’ button in the menu, it displays that:
> Wrote 0 of 1 bytes of the breakin packet.
> Failed to write breakin packet to target. Win32 error 0n87
> WARNING: The HOST cannot communicate with the TARGET!
> But I don’t know how or where I can build a target.
> In other computer, I tried to use command “dbgsrv -t tcp:port=9000” to
> create a debug server(which has a tcp port). But it doesn’t work.
> I also tried to use command “.server tcp:port=9000” to establish a network
> connection. Doesn’t work all the same.
> Does anyone konws this? Very thanks!
> 2009-06-19
>
>
>
> “chandra97 97” wrote in message news:xxxxx@windbg…
>>The timestamp towards title is “Monday, February 09, 2009 2:20 PM”. What I
>>understood is OP is asking >about debugging a remote machine over the
>>network.
> While the article is welcome, it involves an extra computer system which
> is
> pre setup. The same could be achieved by using a remote desktop
> connection.
> Meanwhile the actual kernel debugging connection is still over a serial
> cable or firewire. In absence of a fully functional local kernel
> debugger,
> remote kernel debugging over a network will reduce the pain by giving
> great
> flexibility.
> //Daniel
> —
> WINDBG is sponsored by OSR
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4171 (20090619)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4171 (20090619)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Wow, this thread really came full circle…
-scott
–
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com
“Don Burn” wrote in message news:xxxxx@windbg…
> Go back and look at the link Scott provided. This is an in house stuff
> that an interface leaked out.
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
> “changpei1982” wrote in message
> news:xxxxx@windbg…
>>
>> Hi, guys!
>> I have noticed the net table in the ‘kernel debugging’ page too. Today I
>> tried to make it work, but failed. I select the net table and input a
>> port number to it and then click OK, it will build a host client. Then I
>> click the ‘break’ button in the menu, it displays that:
>> Wrote 0 of 1 bytes of the breakin packet.
>> Failed to write breakin packet to target. Win32 error 0n87
>> WARNING: The HOST cannot communicate with the TARGET!
>> But I don’t know how or where I can build a target.
>> In other computer, I tried to use command “dbgsrv -t tcp:port=9000” to
>> create a debug server(which has a tcp port). But it doesn’t work.
>> I also tried to use command “.server tcp:port=9000” to establish a
>> network connection. Doesn’t work all the same.
>> Does anyone konws this? Very thanks!
>> 2009-06-19
>>
>>
>>
>> “chandra97 97” wrote in message
>> news:xxxxx@windbg…
>>>The timestamp towards title is “Monday, February 09, 2009 2:20 PM”. What
>>>I
>>>understood is OP is asking >about debugging a remote machine over the
>>>network.
>> While the article is welcome, it involves an extra computer system which
>> is
>> pre setup. The same could be achieved by using a remote desktop
>> connection.
>> Meanwhile the actual kernel debugging connection is still over a serial
>> cable or firewire. In absence of a fully functional local kernel
>> debugger,
>> remote kernel debugging over a network will reduce the pain by giving
>> great
>> flexibility.
>> //Daniel
>> —
>> WINDBG is sponsored by OSR
>> For our schedule of WDF, WDM, debugging and other seminars visit:
>> http://www.osr.com/seminars
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>>
>> Information from ESET NOD32 Antivirus, version of virus
>> signature database 4171 (20090619)
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4171 (20090619)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
Scott,
We point people to the archives all the time, just view this as an
accelerated version of that.
Don
“Scott Noone” wrote in message news:xxxxx@windbg…
> Wow, this thread really came full circle…
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> “Don Burn” wrote in message news:xxxxx@windbg…
>> Go back and look at the link Scott provided. This is an in house stuff
>> that an interface leaked out.
>>
>>
>> –
>> Don Burn (MVP, Windows DDK)
>> Windows Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/WinDrvr
>>
>> “changpei1982” wrote in message
>> news:xxxxx@windbg…
>>>
>>> Hi, guys!
>>> I have noticed the net table in the ‘kernel debugging’ page too. Today
>>> I tried to make it work, but failed. I select the net table and input a
>>> port number to it and then click OK, it will build a host client. Then
>>> I click the ‘break’ button in the menu, it displays that:
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. Win32 error 0n87
>>> WARNING: The HOST cannot communicate with the TARGET!
>>> But I don’t know how or where I can build a target.
>>> In other computer, I tried to use command “dbgsrv -t tcp:port=9000” to
>>> create a debug server(which has a tcp port). But it doesn’t work.
>>> I also tried to use command “.server tcp:port=9000” to establish a
>>> network connection. Doesn’t work all the same.
>>> Does anyone konws this? Very thanks!
>>> 2009-06-19
>>>
>>>
>>>
>>> “chandra97 97” wrote in message
>>> news:xxxxx@windbg…
>>>>The timestamp towards title is “Monday, February 09, 2009 2:20 PM”. What
>>>>I
>>>>understood is OP is asking >about debugging a remote machine over the
>>>>network.
>>> While the article is welcome, it involves an extra computer system which
>>> is
>>> pre setup. The same could be achieved by using a remote desktop
>>> connection.
>>> Meanwhile the actual kernel debugging connection is still over a serial
>>> cable or firewire. In absence of a fully functional local kernel
>>> debugger,
>>> remote kernel debugging over a network will reduce the pain by giving
>>> great
>>> flexibility.
>>> //Daniel
>>> —
>>> WINDBG is sponsored by OSR
>>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> http://www.osr.com/seminars
>>> To unsubscribe, visit the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>>>
>>>
>>>
>>> Information from ESET NOD32 Antivirus, version of virus
>>> signature database 4171 (20090619)
>>>
>>> The message was checked by ESET NOD32 Antivirus.
>>>
>>> http://www.eset.com
>>>
>>>
>>>
>>
>>
>>
>> Information from ESET NOD32 Antivirus, version of virus
>> signature database 4171 (20090619)
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4171 (20090619)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4171 (20090619)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
All these msgs could be shortened by one straight answer, link that original answer, if it still there.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: 19 June, 2009 5:18 PM
To: Kernel Debugging Interest List
Subject: Re:[windbg] Re:debugging over network
Scott,
We point people to the archives all the time, just view this as an
accelerated version of that.
Don
“Scott Noone” wrote in message news:xxxxx@windbg…
> Wow, this thread really came full circle…
>
> -scott
>
> –
> Scott Noone
> Consulting Associate
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> “Don Burn” wrote in message news:xxxxx@windbg…
>> Go back and look at the link Scott provided. This is an in house stuff
>> that an interface leaked out.
>>
>>
>> –
>> Don Burn (MVP, Windows DDK)
>> Windows Filesystem and Driver Consulting
>> Website: http://www.windrvr.com
>> Blog: http://msmvps.com/blogs/WinDrvr
>>
>> “changpei1982” wrote in message
>> news:xxxxx@windbg…
>>>
>>> Hi, guys!
>>> I have noticed the net table in the ‘kernel debugging’ page too. Today
>>> I tried to make it work, but failed. I select the net table and input a
>>> port number to it and then click OK, it will build a host client. Then
>>> I click the ‘break’ button in the menu, it displays that:
>>> Wrote 0 of 1 bytes of the breakin packet.
>>> Failed to write breakin packet to target. Win32 error 0n87
>>> WARNING: The HOST cannot communicate with the TARGET!
>>> But I don’t know how or where I can build a target.
>>> In other computer, I tried to use command “dbgsrv -t tcp:port=9000” to
>>> create a debug server(which has a tcp port). But it doesn’t work.
>>> I also tried to use command “.server tcp:port=9000” to establish a
>>> network connection. Doesn’t work all the same.
>>> Does anyone konws this? Very thanks!
>>> 2009-06-19
>>>
>>>
>>>
>>> “chandra97 97” wrote in message
>>> news:xxxxx@windbg…
>>>>The timestamp towards title is “Monday, February 09, 2009 2:20 PM”. What
>>>>I
>>>>understood is OP is asking >about debugging a remote machine over the
>>>>network.
>>> While the article is welcome, it involves an extra computer system which
>>> is
>>> pre setup. The same could be achieved by using a remote desktop
>>> connection.
>>> Meanwhile the actual kernel debugging connection is still over a serial
>>> cable or firewire. In absence of a fully functional local kernel
>>> debugger,
>>> remote kernel debugging over a network will reduce the pain by giving
>>> great
>>> flexibility.
>>> //Daniel
>>> —
>>> WINDBG is sponsored by OSR
>>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> http://www.osr.com/seminars
>>> To unsubscribe, visit the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>>>
>>>
>>>
>>> Information from ESET NOD32 Antivirus, version of virus
>>> signature database 4171 (20090619)
>>>
>>> The message was checked by ESET NOD32 Antivirus.
>>>
>>> http://www.eset.com
>>>
>>>
>>>
>>
>>
>>
>> Information from ESET NOD32 Antivirus, version of virus
>> signature database 4171 (20090619)
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4171 (20090619)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4171 (20090619)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
—
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
?This e-mail is sent on the Terms and Conditions that can be accessed by Clicking on this link http://www.vodacom.co.za/legal/email.jsp "
Hi Don!
HaHa! Interesting! Sorry for missing the link Scott provided at the beginning. It will be very cool to kernel debug over network. I have just made my laptop's 1394 port broken. If this funcion can comes true soon, I will don't need to buy a new one.
2009-06-19
Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
"changpei1982" wrote in message
news:xxxxx@windbg...
>
> Hi, guys!
> I have noticed the net table in the 'kernel debugging' page too. Today I
> tried to make it work, but failed. I select the net table and input a
> port number to it and then click OK, it will build a host client. Then I
> click the 'break' button in the menu, it displays that:
> Wrote 0 of 1 bytes of the breakin packet.
> Failed to write breakin packet to target. Win32 error 0n87
> WARNING: The HOST cannot communicate with the TARGET!
> But I don't know how or where I can build a target.
> In other computer, I tried to use command "dbgsrv -t tcp:port=9000" to
> create a debug server(which has a tcp port). But it doesn't work.
> I also tried to use command ".server tcp:port=9000" to establish a network
> connection. Doesn't work all the same.
> Does anyone konws this? Very thanks!
> 2009-06-19
>
>
>
> "chandra97 97" wrote in message news:xxxxx@windbg...
>>The timestamp towards title is "Monday, February 09, 2009 2:20 PM". What I
>>understood is OP is asking >about debugging a remote machine over the
>>network.
> While the article is welcome, it involves an extra computer system which
> is
> pre setup. The same could be achieved by using a remote desktop
> connection.
> Meanwhile the actual kernel debugging connection is still over a serial
> cable or firewire. In absence of a fully functional local kernel
> debugger,
> remote kernel debugging over a network will reduce the pain by giving
> great
> flexibility.
> //Daniel
> ---
> WINDBG is sponsored by OSR
> For our schedule of WDF, WDM, debugging and other seminars visit:
> OSR Seminars – OSR
> To unsubscribe, visit the List Server section of OSR Online at
> ListServer/Forum
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4171 (20090619)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4171 (20090619)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
---
WINDBG is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
OSR Seminars – OSR
To unsubscribe, visit the List Server section of OSR Online at ListServer/Forum