Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
oBFusCATed:
And another one: http://smrt.is-a-geek.org/codeblocks/patches/dbg/dbg_refactor0016.1.patch
Fixed this bug:
--- Quote from: Ceniza on August 22, 2010, 04:29:17 pm ---
At first no window was ticked. I clicked on "Watches" (which was already visible), and it go its tick. Disassembly window was not shown. I clicked on it, I got it, and the tick was also there. CPU Registers was shown from the beginning, never clicked it, never got the tick.
--- End quote ---
cbexaminr:
FWIW -
In svn branch wxpropgrid_debugger, file plugins\debuggergdb\gdb_commands.h, "class GdbCmd_TooltipEvaluation", routine "void ParseOutput(const wxString& output)", toward the end of the routiine, I think there is a problem with the variable s_pWin.
It appears some code was added (relative to current trunk) to avoid invoking the tipwindow if the mouse has moved. As a result of that addition, it seems s_pWin can be left with a value of an item that was "Close()"ed in a previous iteration, such that subsequent attempts to "Close()" that old item could occur, which might be a bad thing.
Didn't see anywhere else where s_pWin was being cleared to avoid this potential problem, but I may be overlooking something - and I don't know for sure that the "Close()" will render the item invalid, but...
it looks suspicious to me.
oBFusCATed:
Will look at it...
oBFusCATed:
Next patch: http://smrt.is-a-geek.org/codeblocks/patches/dbg/dbg_refactor0016.3.1.patch
1. Added s_pWin = NULL in GdbCmd_TooltipEvaluation::ParseOutput
2. Added the check if the terminal opening has finished in a loop. The terminal should open faster. Also it should be detected correctly if it is started on a slower computer.
3. Fixed parsing of std::string = "test,test" in the watches window
4. Fixed "Catch exception" on windows
5. Fixed some "Do not run debuggee bugs"
5.1. "tbreak" command was emitted, when the debug/continue button was hit
5.2. "run" command was emitted, when in remote debugging mode, now emits the correct "cont"
5.3. "start" command was emitted, now the correct "run" is emitted
Test please :)
oBFusCATed:
Next patch: http://smrt.is-a-geek.org/codeblocks/patches/dbg/dbg_refactor0016.4.patch
1. Combined "Debug -> Start" and "Debug -> Continue" in one menu item
2. Moved "Debug -> Run to Cursor" below "Stop debugger"
3. Implemented interrupting the debugger while remote debugging (see this thread for details http://forums.codeblocks.org/index.php/topic,12412.0.html )
4. Fixed a warning
Test again please...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version