Remote Debugging - Target 64 bit Vista + Host 32 bit XP

[anshul]

Hi,

I am trying to setup kernel debug environment to debug printer driver
installed on Vista 64 Bit.

My target system is Windows Vista 64 bit where the driver will be
installed.

My host system is Windows XP 32 bit.

I am try to do serial port debugging.

Using bcdedit, I have enabled kernel debugging on Vista system and
specified com 1 as the debug port.

Then I installed debugging tools for 32 bit on XP system.

After I reboot Windows Vista system, no connection is established with
windbg launched on Windows XP 32 bit. As a result I am unable to see
any trace messages or put any breakpoint.

Another thing I noticed is that, com port is automatically uninstalled
and doesnt show up in device manger after remote kernel debugging has
been enabled in Vista.

Please help. If you have any idea or reference then kindly share it.

Thanks

[Goldbach]

May be it will be a little help for you.
Take a look at:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=720298&SiteID=1

--
If the message was helpful to you, please click "Yes", next to "Was this
post helpful to you?"

Regards,
Goldbach

[anshul]

On May 22, 6:53 pm, Goldbach <Goldb...@discussions.microsoft.com>
wrote:

> > Thanks- Hide quoted text -
>
> - Show quoted text -

Thanks for the reply.
But I want to do remote debugging using windbg not visual studio and
the link does not talk about that.

My windbg is installed on XP system running in 32 bit mode . And
printer driver is installed on Vista 64 bit.

Thanks

[Don Burn]

First does the serial link work with hyperterminal running on each system
(i.e. type into one system see the characters on the other, then try the
second system). Did you specify the baudrate in BCDEdit and does it match
the one in Windbg (and the speed you used to test with hyperterminal).

The lack of the COM port on the test system is standard, the port is now
owned by the debugger not by the serial port driver.

--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

"anshul" <anshul...@gmail.com> wrote in message
news:1179816066....@w5g2000hsg.googlegroups.com...

[anshul]

On May 22, 11:01 pm, "Don Burn" <b...@stopspam.windrvr.com> wrote:
> First does the serial link work with hyperterminal running on each system
> (i.e. type into one system see the characters on the other, then try the
> second system). Did you specify the baudrate in BCDEdit and does it match
> the one in Windbg (and the speed you used to test with hyperterminal).
>
> The lack of the COM port on the test system is standard, the port is now
> owned by the debugger not by the serial port driver.
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Website:http://www.windrvr.com
> Blog:http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>

> "anshul" <anshulmak...@gmail.com> wrote in message

>
> news:1179816066....@w5g2000hsg.googlegroups.com...
>
>
>
> > Hi,
>
> > I am trying to setup kernel debug environment to debug printer driver
> > installed on Vista 64 Bit.
>
> > My target system is Windows Vista 64 bit where the driver will be
> > installed.
>
> > My host system is Windows XP 32 bit.
>
> > I am try to do serial port debugging.
>
> > Using bcdedit, I have enabled kernel debugging on Vista system and
> > specified com 1 as the debug port.
>
> > Then I installed debugging tools for 32 bit on XP system.
>
> > After I reboot Windows Vista system, no connection is established with
> > windbg launched on Windows XP 32 bit. As a result I am unable to see
> > any trace messages or put any breakpoint.
>
> > Another thing I noticed is that, com port is automatically uninstalled
> > and doesnt show up in device manger after remote kernel debugging has
> > been enabled in Vista.
>
> > Please help. If you have any idea or reference then kindly share it.
>

> > Thanks- Hide quoted text -
>
> - Show quoted text -

Hi,

Thanks for the suggestion.

I tried to communicate using hyper terminal using serial port and its
working.

Then I tested the remote debugging on WinXP 64 bit and WinXP 32 bit ,
that also worked.

I also verified debug settings in vista using BCDEdit , all are fine.

But still there is no communication between Windbg on XP32 bit and
Vista 64 bit debug mode..

Please if you have any suggestion or any hint then do share it.

Thanks.

[Ivan Brugiolo [MSFT]]

Can you post the output of `bcdedit /enum` ?
And, can you enable both boot-debugging and debugging ?
`bcdedit /bootdebug {current} on`
`bcdedit /debug {current} on`
Then, can you try to have the debugger
host running before you reboot the target ?

You should see something like:

BD: Boot Debugger Initialized
Connected to Windows Boot Debugger 6427 x86 compatible target, ptr64 FALSE
Kernel Debugger connection established.

Then, try CTRL-D, and watch the sequence of packet being exchanged.

--
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"anshul" <anshul...@gmail.com> wrote in message

news:1179895369....@k79g2000hse.googlegroups.com...