[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[cdt-debug-dev] Notes about testing the WinDbg pluggin.
|
Hello Douglas
Here are some notes about testing the pluggin.
There could be an error in the cpp files that goes like this:
All the cpp files are missing the "core" in this lines
"Java_org_eclipse_cdt_debug_win32_core"
I.e. theNATIVE defines have wrong package name!
Fixing this and rebuilding the dll resulted in success!
Now the run-time workbench launch and the debugger
Can be selected.
There are some messages popping up when I start Debugging.
Also it does not stop at my breakpoint. (probably the messages are the reason).
However! the output for the code is properly displayed in the Console "hello yo!15"
This is the C code used:
int main() {
int x = 10;
x+=5;
cout <<"hello yo!" << x;
return 0;
}
Messages and Console output are in the order they hit me.
Dialog Caption = "ModeInfo"
Message = "The parameter is incorrect."
Dialog Caption = "LineInfo"
Message = "The specified module could not be found."
Dialog Caption = "Breakpoint Read Memory"
Message = "Only part of a ReadProcessMemory or WriteProcessMemory request was completed."
- The Console windows in Eclipse are now showing me this message "Error in SymFromName for 'main'"
Dialog Caption = "SymFromName"
Message = "The specified module could not be found"
Dialog Caption = "Breakpoint Read Memory"
Message = "Only part of a ReadProcessMemory or WriteProcessMemory request was completed."
Another observation we did was when distriubuting the pluggin.
The debugger name in the Run-Time workbench are "Win32 Debugger"
In the distributed and installed pluggin the name are "%debuggerName"
Also the above messages show up in the distributed and installed pluggin.
Maybe we have forgotten some workbench setting or other System setup stuff and this
results in the errors we observer. In this case hopefully you have patience and can explain
the essence of this! Grate work Doug!, look forward to see the progress on this pluggin.
--
Best regards,
Hasse mailto:hasse@xxxxxxxxxxxxxxx