Splitting debugger in two - specific debugger and common GUI

[oBFusCATed]

Another stable patch: http://smrt.is-a-geek.org/codeblocks/patches/dbg/dbg_refactor0016.7.1.patch

All changes from the previous patch plus:
4. Fixed the examine memory parser problem described here: http://forums.next.codeblocks.org/index.php/topic,13273.new.html
5. Replaced \\t with \t, because it seems that wxRegEx doesn't support '\\t' by default, wxRE_ADVANCED should be used

[MortenMacFly]

Another stable patch: http://smrt.is-a-geek.org/codeblocks/patches/dbg/dbg_refactor0016.7.1.patch

The other one (http://smrt.is-a-geek.org/codeblocks/patches/dbg/dbg_refactor0017.3.patch) now won't apply anymore btw...

[oBFusCATed]

Yes, the patches has duplicate changes, if you remove the duplicates it should apply
If not I'll fix it tonight...

[oBFusCATed]

Next stable patch: http://smrt.is-a-geek.org/codeblocks/patches/dbg/dbg_refactor0016.8.patch

1. Added UpdateUI event for the controls used for sending commands to debugger.
2. Commands send from the normal log ("Debugger") print their result to both logs.
3. Some cleaning

Please test

[cbexaminr]

Is there currently a debugging step capability within something like the disassembly window?

If not, do you have any plans, or know if others do, to add one?

[oBFusCATed]

Have you tried the "next instruction" and the new "step into instruction" commands?

[cbexaminr]

No - hadn't taken note of those.  Maybe because when I use them (I might have tried them before), while stepping does seem to occur, and I see the related actions in the Debugger (debug) log panel, I don't see any results anywhere else.

Is there some visual tracking of the process available outside of the log panel?  If so, where, how activated?  (I've looked at the Debug disassembly window, and it doesn't seem to be tracking anything there.)

Thanks.

[oBFusCATed]

Is there some visual tracking of the process available outside of the log panel?  If so, where, how activated?  (I've looked at the Debug disassembly window, and it doesn't seem to be tracking anything there.)

You've to see the same yellow arrow in the Disassembly window, as with the normal editor.

If you don't see it, please post details in this thread: http://forums.next.codeblocks.org/index.php/topic,12873.new.html

[cbexaminr]

If you don't see it, please post details in this thread: http://forums.next.codeblocks.org/index.php/topic,12873.new.html

didn't see it.
observations posted.

[oBFusCATed]

Morten:
this change is wrong, please revert it:

Code Select Expand


obfuscated@xlad ~/projects/codeblocks/brances/wxpropgrid_debugger $ svn diff -r PREV:HEAD src/sdk/loggers.cpp
Index: src/sdk/loggers.cpp
===================================================================
--- src/sdk/loggers.cpp (revision 6605)
+++ src/sdk/loggers.cpp (revision 6608)
@@ -103,7 +104,6 @@

     style[success].SetTextColour(BlendTextColour(*wxBLUE));

-    style[warning].SetTextColour(BlendTextColour(*wxBLUE));
     style[warning].SetFont(italic_font);

     style[error].SetFont(bold_font);


[MortenMacFly]

this change is wrong, please revert it:

Code Select Expand


-    style[warning].SetTextColour(BlendTextColour(*wxBLUE));
     style[warning].SetFont(italic_font);


It's not applied anyways in the debugger branch's HEAD. :-)

[oBFusCATed]

It was applied...  :?

[MortenMacFly]

It was applied...  :?

It was removed during the merge... Probably not on purpose, but it's OK as it seems. :-)

[oBFusCATed]

It was removed during the merge... Probably not on purpose, but it's OK as it seems. :-)

I've added the change because in the gdb_mi plugin it was not OK, I don't know why.

[cbexaminr]

Obfusc, have you overlooked:
http://forums.next.codeblocks.org/index.php/topic,12501.msg89687.html#msg89687

or just not had time, or (relatively sufficient) interest?