Native VS Debugger Question - SOLVED
-
Is it possible in the Visual Studio native debugger to navigate to a symbol's location (in disassembly view) by using the name of the symbol? For instance, going to the start of the GetLastError() function by entering the name of it? If so, how does one do this? EDIT: If VS can't do this, can KDebug do it? SOLUTION: On the Visual Studio DEBUG menu, choose New Breakpoint => Function Breakpoint and then enter the name of the DLL and the function name as such:
ws2_32.dll!socket
It will place a breakpoint at the beginning of the function!
The difficult we do right away... ...the impossible takes slightly longer.
-
Is it possible in the Visual Studio native debugger to navigate to a symbol's location (in disassembly view) by using the name of the symbol? For instance, going to the start of the GetLastError() function by entering the name of it? If so, how does one do this? EDIT: If VS can't do this, can KDebug do it? SOLUTION: On the Visual Studio DEBUG menu, choose New Breakpoint => Function Breakpoint and then enter the name of the DLL and the function name as such:
ws2_32.dll!socket
It will place a breakpoint at the beginning of the function!
The difficult we do right away... ...the impossible takes slightly longer.
I just tried getting the address in the debug window but could not find any way to do it. But if you add a call to GetLastError and set a breakpoint at that address, the debugger will stop at the call. I am not sure what you would gain by it even if you could find the address, since you cannot step into most Window functions.
-
I just tried getting the address in the debug window but could not find any way to do it. But if you add a call to GetLastError and set a breakpoint at that address, the debugger will stop at the call. I am not sure what you would gain by it even if you could find the address, since you cannot step into most Window functions.
Richard MacCutchan wrote:
I am not sure what you would gain by it even if you could find the address
I must debug an executable for which I do not have the source, and I need to determine which Winsock mode it's using, overlapped I/O, completion ports, select event, etc. I figured I would do this by placing breakpoints at all of the various Winsock functions and examining the arguments being passed.
The difficult we do right away... ...the impossible takes slightly longer.
-
Richard MacCutchan wrote:
I am not sure what you would gain by it even if you could find the address
I must debug an executable for which I do not have the source, and I need to determine which Winsock mode it's using, overlapped I/O, completion ports, select event, etc. I figured I would do this by placing breakpoints at all of the various Winsock functions and examining the arguments being passed.
The difficult we do right away... ...the impossible takes slightly longer.
Without the source you will not be able to see very much. The debugger only works with the debug information created by the compiler and linker, and built into the PDB file. Without that and the source files you will most likely not be able to find anything.
