Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
someone working on CDB debugger?
Martin K.:
--- Quote from: MortenMacFly on October 11, 2012, 05:48:35 pm ---
--- Quote from: Martin K. on October 11, 2012, 02:11:24 pm ---Any Ideas?
--- End quote ---
Hopefully oBFusCATed can say something more detailed about this, but weren't there just with the last commits some changes accordingly to fix a (similar/same) wrong behaviour accordingly? Are your sources in sync with trunk?
--- End quote ---
yes, my sources are compiling fine to the trunk.
Martin
oBFusCATed:
ShiftBreakpoint function should re-set the breakpoint only if the compiler supports edit-and-continue, but c::b currently doesn't support edit-and-continue.
I'm not sure what is the best action we could take. The options are:
1. Mark the breakpoint as invalid (should provide some api for it)
2. Don't move the breakpoints and tell the editor that the must stay at the same line as before the edit operation, thus the breakpoint and the source will diverge.
3. Anything else...
Martin K.:
OK,
i do what M$ does, what the best solution is - maybe. Warn the user about the changes, update the editor marks and let the debugger run into the wrong breakpoint position.
Martin
BTW: I like to have the possibility to load a source file into the editor, which is not known to the project. Why? For example, i have installed wxWidgets from wxPack. my path for the installation is c:\codeblocks\wxWidgets2.8.12. When i debug an application and break (or step) into the wxWidgets library, than CDB gives me symbols for the original path where the library was build from by someone who builds wxPack. My project has never build the library and my paths are not the same a those be used from the wxPack team. So i like to open source files like the WinDbg debugger will open it, or i like to let the user define some type of replace-mask, so that he (or i :-) can step into the library source (or any other source) without having them to be in the same path as the library creator. Any suggestions on this? SyncEditor calls always the project file functions.
thanks Martin
oBFusCATed:
--- Quote from: Martin K. on October 11, 2012, 11:04:48 pm ---SyncEditor calls always the project file functions.
--- End quote ---
As far as I can see it should work if you pass the correct path to the file on your system. Have you tried it?
Martin K.:
--- Quote from: oBFusCATed on October 11, 2012, 11:53:15 pm ---
--- Quote from: Martin K. on October 11, 2012, 11:04:48 pm ---SyncEditor calls always the project file functions.
--- End quote ---
As far as I can see it should work if you pass the correct path to the file on your system. Have you tried it?
--- End quote ---
no, i have not tried it, i have had only a look at the source code - too many construction sites...
I will try it next week, because i am on a short vacation this weekend (vienna).
Martin
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version