Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
DDD-like watches
Michael:
--- Quote from: Ceniza on January 10, 2006, 10:17:24 pm ---
--- Quote from: lord mandrav ---I see no reason for graphical gizmos in a debugger. Really, what do you need that for?
--- End quote ---
It isn't a need, I just like to "visualize" things better, and it seems I'mn't alone :)
--- End quote ---
No you are not alone :). I think it is important (at least for me :)) to provide a clear, easy-to-understand, scalable view of the debugger info.
--- Quote from: Ceniza on January 10, 2006, 10:17:24 pm ---(Code::Blocks 7.0 maybe?) :)
--- End quote ---
C::B 7.0? :D
Michael
m.29:
Hi, I'm opening this old topic because I would like to implement some functionality of DDD to Code::Blocks. As I noticed, new features to debugger are added by editing the code in plugins/debuggergdb/ directory. But I try add new functionality by pure new plugin. This is my test code:
--- Code: ---void DDDLikeWatches::OnAttach()
{
cbDebuggerPlugin *debugger = reinterpret_cast<cbDebuggerPlugin *>(
Manager::Get()->GetPluginManager()->FindPluginByName(wxT("Debugger"))
);
DebuggerGDB *gdb = reinterpret_cast<DebuggerGDB *>(debugger);
DebuggerDriver *driver = gdb->GetState().GetDriver();
}
--- End code ---
When I try compile this, I get undefined reference to `DebuggerState::GetDriver()'. My question is: Where is the problem? Can I access debugger's functions from debugger.dll from other plugin or must modify original debugger plugin's code to add this functionality to debugger? I link debugger.dll to my project.
MortenMacFly:
--- Quote from: m.29 on January 22, 2011, 01:36:31 pm ---Where is the problem? Can I access debugger's functions from debugger.dll from other plugin or must modify original debugger plugin's code to add this functionality to debugger? I link debugger.dll to my project.
--- End quote ---
You should link against the SDK, not the plugin. BTW: If you are working on the debugger, make sure you are using the debugger branch as:
1.) Your features might already have been implemented there
2.) We will sooner or later switch to this branch, so your changes to trunk might be very hard to integrate later.
m.29:
Thanks for your reply. I'm linking against SDK too (codeblocks.dll).
1.) Feature that I try implement is Graphical Inspection of Data Structures and viewing them like oriented graphs. This feature isn't implemented there.
2.) As I noticed in SVN:
--- Quote ---debugger_branch: merged with trunk (trunk to debugger_branch)
--- End quote ---
So I use trunk.
Because, I don't know how to link debugger's functions, I'll try edit original sources to add this functionality.
MortenMacFly:
--- Quote from: m.29 on January 22, 2011, 10:33:41 pm ---2.) As I noticed in SVN:
--- Quote ---debugger_branch: merged with trunk (trunk to debugger_branch)
--- End quote ---
So I use trunk.
--- End quote ---
Please read carefully, it's written there: trunk to debugger_branch. Thus, features implemented in trunk not yet in the debugger branch have been merged. Still it will always be as : debugger branch = trunk + debugger related modifications. Thats what the branch is for, it has a way different (re-factored) implementation of th debugger.
Once the debugger branch comes merged into trunk, there won't be a need for this branch anymore and it'll be closed. For now, all debugger related development is there and only there.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version