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

Splitting debugger in two - specific debugger and common GUI

<< < (77/136) > >>

MortenMacFly:

--- Quote from: oBFusCATed on February 03, 2011, 09:14:16 am ---Morten: go go go with the commit :)

--- End quote ---
...done. Good work!

oBFusCATed:
Thanks Morten, you can close the patches in Berlios, if you've not done so already  8)

dmoore:
Obfuscated: Any chance you can help me use your Debugger API to write a plugin for Python debugging? (I have some very old code -- a massive hack -- where I tried to do this but your work would make it much simpler and better integrated). And by "help", I mean tell me what to look at to get started, tell me what I'm doing wrong when I hit a wall etc. You don't have to provide any code.

oBFusCATed:
Yes, I can and I will be glad :)

The two things you can look at are the debugger plugin in the cb's svn and my try at gdb/mi plugin.
My plugin can be accessed with svn at svn://smrt.is-a-geek.org/cb_gdb_mi/debbugger_gdbmi (at the moment I think it fails to compile).

The basic idea is: you make a plugin, derive from cbDebuggerPlugin, then you implement all the virtual methods :)

Take a look at both plugins and if you have questions ask :)

dmoore:
I spent an hour or so today looking through the code. I think I have a rough understanding of the new features. I have a few basic questions.

1. Just to be sure, is the latest SDK code here:

svn checkout http://svn.berlios.de/svnroot/repos/codeblocks/branches/wxpropgrid_debugger

To save me some reading/testing:

2. How does the handling of multiple debuggers work? Do they all share the same ui elements? What happens when a user switches between debuggers using the active debugger menu option? (e.g. what happens to the ui elements such as the watch, stack etc?) If plugin 1 is already debugging, can I switch to plugin2 and start a new debugging session and keep the session in plugin1 active? (And will the framework update the ui appropriately when I switch between them?)

3. For a python application, it probably makes the most sense to start debugging the active file in the editor (rather than the active target). Is that going to be a problem?

4. What is the purpose of OnAttachReal/OnReleaseReal? I hope we never see OnAttachReallyReallyReal :)

Thanks for the good work on this, oBFusCATed.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version