No reference to source code after break.

Hello,
I am using VirtualBox and try to remote debug a 64 bit app. The Target
is on an IA64 machine with Win 7. From host I passed the local path to
source code in ‘File > “Source File Path…”’ but I don’t get any source
code, no disassembly or any symbols, when breaking in my code. Please help.
I noticed that for some reasons the local executable path from a
previous project is still showing in the output:“Executable search path
is: C:\W…”, theres also no line for the local source path printed but
I configured it like i already said.

Thanks for reading so far, sorry for my bad english, hope you get me.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \.\pipe\kd_win7_64
Waiting to reconnect…
Connected to Windows 7 7600 x64 target at (Tue Oct 25 20:26:54.590 2011
(UTC + 2:00)), ptr64 TRUE
Kernel Debugger connection established. (Initial Breakpoint requested)
Symbol search path is:
srv*C:\WINDOWS\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
C:\WinDDK\7600.16385.1\src\mydriver\hellowrld\objfre_win7_x86\i386
Windows 7 Kernel Version 7600 MP (1 procs) Free x64
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff80002604000 PsLoadedModuleList = 0xfffff80002841e50
System Uptime: not available
Break instruction exception - code 80000003 (first chance)
*******************************************************************************
*
*
* You are seeing this message because you pressed either
*
* CTRL+C (if you run kd.exe) or,
*
* CTRL+BREAK (if you run WinDBG),
*
* on your debugger machine’s keyboard.
*
*
*
* THIS IS NOT A BUG OR A SYSTEM CRASH
*
*
*
* If you did not intend to break into the debugger, press the “g” key,
then *
* press the “Enter” key now. This message might immediately reappear.
If it *
* does, press “g” and “Enter” again.
*
*
*
*******************************************************************************
nt!DbgBreakPointWithStatus:
fffff8000266df60 cc int 3 kd\> bc \* kd\> g The context is partially valid. Only x86 user-mode context is available. WOW64 breakpoint - code 4000001f (first chance) First chance exceptions are reported before any exception handling. This exception may be expected and handled. 0000000012bb4a69 cc int 3
32.kd:x86> p
The context is partially valid. Only x86 user-mode context is available.
The context is partially valid. Only x86 user-mode context is available.
The context is partially valid. Only x86 user-mode context is available.
0000000012bb4a6a e8efa6ffff call 12baf15e 32.kd:x86\> p The context is partially valid. Only x86 user-mode context is available. 0000000012bb4a6f 68e0edc012 push 12C0EDE0h
32.kd:x86> p
The context is partially valid. Only x86 user-mode context is available.
00000000`12bb4a74 e87fb7ffff call 12bb01f8
32.kd:x86> p

benny_reichelt wrote:

Hello,
I am using VirtualBox and try to remote debug a 64 bit app. The Target
is on an IA64 machine with Win 7.

No, it’s not. It’s an x64 machine. The two architectures are
COMPLETELY different.

Are you quite sure you are running a 64-bit application? The second
break that you hit, exception 0x4000001f, is the one you get when a you
run a 32-bit application, at the moment the process transitions to
32-bit mode.

In general, it is not productive to debug user-mode applications using
the kernel debugger. If you are trying to do application debug, there
are better ways.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.