Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Splitting debugger in two - specific debugger and common GUI

<< < (74/136) > >>

killerbot:
oh yes, I am just waiting for a merge of the trunk to debugger branch, we want some goodies from that one first ;-)

MortenMacFly:

--- Quote from: killerbot on December 18, 2010, 04:40:47 pm ---oh yes, I am just waiting for a merge of the trunk to debugger branch, we want some goodies from that one first ;-)

--- End quote ---
Go ahead! It's all done. ;-)

killerbot:
starting to build, release probably tomorrow morning

oBFusCATed:
Next patch: http://smrt.is-a-geek.org/codeblocks/patches/dbg/dbg_refactor0019.1.patch

Changes:
1. The Watches are refreshed, when the watches dialog is shown and the debugger is running (fixes bug reported by killerbot)
2. Added a virtual method, so a debugger plugin can modify the context menu in the watches dialog (the SDK API is broken)
3. Used the new feature SDK to reimplement "dereference pointer" feature
4. Removed some unused member variables in the class DebuggerGDB

Test please :)

etheranger:
Someone suggested I port my CDB fixes to the branch, so here 'tis (against 6930):

https://developer.berlios.de/patch/index.php?func=detailpatch&patch_id=3122&group_id=5358
Changes:
+ Grab the PID at launch so that process break / killing works - this allows setting breakpoints while running
+ NotifyDebuggeeContinued on Continue so that the cursor doesn't disappear forever after setting breakpoints while running
+ Slightly improve recognising breakpoint & assert hits
+ Added workaround to correctly set working dir (can still be disabled by #undefining ENABLE_WORKINGDIR_WORKAROUND.

I'd appreciate some feedback on the last point at http://forums.codeblocks.org/index.php/topic,14085.0.html if you have an opinion :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page