VMware Communities: Connecting to x64 target ...

VMware

Up to Discussions in Replay-Based Debugging

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)

6 Replies Last post: Jan 31, 2010 10:52 PM by slava_malyugin

Connecting to x64 target posted: Nov 5, 2009 7:41 PM

kernelgrunt

5 posts since
Nov 5, 2009

I am trying to hook up to a Win7 x64 boot in VMWare WS 6.5 using host platform XP x64. GNU gdb 6.3 from MinGW. Settings in vmx file:

bios.bootDelay = "3000"
debugStub.hideBreakpoints = "TRUE"
#debugStub.listen.guest32 = "TRUE"
#debugStub.listen.guest32.remote = "TRUE"
#monitor.debugOnStartGuest32 = "TRUE"
debugStub.listen.guest64 = "TRUE"
debugStub.listen.guest64.remote = "TRUE"

From gdb command-line:

(gdb) set architecture i386:x86-64
The target architecture is assumed to be i386:x86-64
(gdb) target remote localhost:8864
Remote debugging using localhost:8864
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Couldn't establish connection to remote target
Malformed response to offset query, timeout

If I use the 32-bit settings I can connect just fine at boot and step all the way until long mode is enabled.

Using the 64-bit settings I have tried connecting at boot, and I have tried connecting after I know 64-bit instructions are executing. Same behavior...no luck. Am I doing something obviously wrong?

Re: Connecting to x64 target

1. Nov 9, 2009 8:40 AM

in response to: kernelgrunt

kernelgrunt

5 posts since
Nov 5, 2009

I ran the following from a cmd prompt at the point I was trying to connect to 8864:

netstat -an | findstr /i "listening"

and only found 8832 actively listening?? I don't have 8832 setup in my vmx settings? What gives?

Re: Connecting to x64 target

2. Nov 9, 2009 11:11 AM

in response to: kernelgrunt

ecl100

48 posts since
Sep 24, 2007

Hi, kernelgrunt. Would you enter "set debug remote 1" in gdb before "target remote..." and post what you see here?

Re: Connecting to x64 target

3. Nov 9, 2009 11:39 AM

in response to: ecl100

kernelgrunt

5 posts since
Nov 5, 2009

From boot:

(gdb) set debug remote 1
(gdb) target remote localhost:8864
Remote debugging using localhost:8864
Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet: $Hc-1#09..
.Sending packet: $Hc-1#09...Timed out.
Timed out.
Timed out.
Ignoring packet error, continuing...
Sending packet: $qC#b4...Sending packet: $qC#b4...Sending packet: $qC#b4...Sendi
ng packet: $qC#b4...Timed out.
Timed out.
Timed out.
Ignoring packet error, continuing...
Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Sending packet: $q
Offsets#4b...Sending packet: $qOffsets#4b...Timed out.
Timed out.
Timed out.
Ignoring packet error, continuing...
Couldn't establish connection to remote target
Malformed response to offset query, timeout
(gdb)

Re: Connecting to x64 target

4. Nov 9, 2009 3:30 PM

in response to: kernelgrunt

kernelgrunt

5 posts since
Nov 5, 2009

I ran the following from a cmd prompt at the point I was trying to connect to 8864:

netstat -an | findstr /i "listening"

and only found 8832 actively listening?? I don't have 8832 setup in my vmx settings? What gives?

Actually, this wasn't quite right. If I issue the:

netstat -an | findstr /i "listening"

before I attempt to connect, I get the following:

TCP 0.0.0.0:8864 0.0.0.0:0 LISTENING

After the connect attempt fails I run the netstat -an | findstr /i "listening" again and get this:

TCP 0.0.0.0:8832 0.0.0.0:0 LISTENING

How strange?

Re: Connecting to x64 target

5. Nov 9, 2009 3:33 PM

in response to: kernelgrunt

kernelgrunt

5 posts since
Nov 5, 2009

Is there a more appropriate community to post this question too?

Re: Connecting to x64 target

6. Jan 31, 2010 10:52 PM

in response to: kernelgrunt

slava_malyugin

61 posts since
May 14, 2007

Hi kernelgrunt,

You are in the right forum. From the output, I suspect that you are catching boot loader while it is still in the 32-bit mode. You are trying to connect to 64-bit side of the debug stub through port 8864, but stub sends back 32-bit version of registers, confusing the debugger. That would be one possibility, and the other one would be a bug in the debug stub. You may want to try the most recent Workstation build to see if the problem persists, and if so, please try attaching in 32-bit mode. I hope this helps.

Sincerely,

Vyacheslav (Slava) Malyugin

Go to original post

Search VMware Communities Advanced Search

Actions

View as PDF

Up to Discussions in Replay-Based Debugging