Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
dmoore:
--- Quote from: oBFusCATed on February 07, 2011, 03:54:01 pm ---Can you try to return true in IsAttachedToProcess(), for now, later we could fix it correctly.
Please write down every problem you encounter, then give me the list, so I can try to fix them.
--- End quote ---
Yes, I'll try that. I'll also start regularly uploading the python plugin code to my berlios project svn repository so that you can more easily see what I'm talking about (and, if I have time, document my process of writing the plugin a little for future debugger plugin devs).
cbexaminr:
--- Quote from: oBFusCATed on February 07, 2011, 11:08:22 am ---What about integrating your cooker in C::B? :P
--- End quote ---
I would think integrating PLC programming tools would be much more useful for that than my actual cooker.
--- Quote from: oBFusCATed on February 07, 2011, 11:08:22 am ---An IDE imposes some style of work...
--- End quote ---
Lucky for me this is really no different in nature than Attach to process, so its in line with the style of work already supported by C::B (as it allows attaching to any arbitrary process, and does not verify that its one generated by a target of any project that may be open, and does not require any project to be open at all, with the menu option being available without a project.)
--- Quote from: oBFusCATed on February 07, 2011, 11:08:22 am ---I'll look at the patch, but there is a chance that it won't be applied/approved...
--- End quote ---
Any guestimates as to when you will present your opinion on acceptance/denial?
oBFusCATed:
Soon :P :lol:
oBFusCATed:
cbexaminr: You're adding gdb specific stuff in the SDK, this is not right, so you get no as an answer.
Move the GUI inside the gdb plugin and please don't add another Is*Something that should be checked in the UpdateUI methods.
They are pretty messed, so adding more stuff there makes the messier.
BTW: I plan to improve the Settings->Compiler & Debugger -> Debugger.
My current plan is to make it possible to have different debuggers with different settings.
For example: gdb6.8, gdb7.2, gdb for arm, cdb, etc.
And then in the compilers settings you'll have a wxChoice control, so you can choose one of the debuggers.
There will be a default debugger (I've not thought about it much). And if there is not project opened we could
interpret Debug->Start as the StartExternalProcess in your patch, but changes should be handled internally (inside the specific plugin).
p.s. there is wxEmptyString, use it instead of _(""), also use _("...") only when you want the string to be translatable, else use wxT("...") or _T("...")
cbexaminr:
--- Quote from: oBFusCATed on February 08, 2011, 12:51:44 am ---cbexaminr: You're adding gdb specific stuff in the SDK, <snip>
--- End quote ---
I don't think so. I assume you're referring to the...
--- Quote from: oBFusCATed on February 08, 2011, 12:51:44 am --- Move the GUI inside the gdb plugin
--- End quote ---
GUI, which should be serving both GDB and CDB, but I will verify. (I was hoping someone else might verify that path since I'm not set up with CDB available currently.)
--- Quote from: oBFusCATed on February 08, 2011, 12:51:44 am ---and please don't add another Is*Something that should be checked in the UpdateUI methods.
They are pretty messed, so adding more stuff there makes the messier.
--- End quote ---
What then, is the currently available alternative, to determine that the debugging toolbar icons and menu options should be enabled/available? (The IsExternalProcess() was just following the pattern established by the previously existing IsAttachedToProcess() functionality.) I would have guessed the presence of m_activeDebugger to be enough, but the previously existing code in DebuggerMenu suggests not...???
--- Quote from: oBFusCATed on February 08, 2011, 12:51:44 am ---BTW: I plan to improve the Settings->Compiler & Debugger -> Debugger.
My current plan is to make it possible to have different debuggers with different settings.
For example: gdb6.8, gdb7.2, gdb for arm, cdb, etc.
And then in the compilers settings you'll have a wxChoice control, so you can choose one of the debuggers.
There will be a default debugger (I've not thought about it much). And if there is not project opened we could
interpret Debug->Start as the StartExternalProcess in your patch, but changes should be handled internally (inside the specific plugin).
--- End quote ---
Neither of Debug/Start-Continue menu option nor related toolbar icon are currently enabled in that circumstance. How will you deal with that?
--- Quote from: oBFusCATed on February 08, 2011, 12:51:44 am ---p.s. there is wxEmptyString, use it instead of _(""), also use _("...") only when you want the string to be translatable, else use wxT("...") or _T("...")
--- End quote ---
OK, I have not previously understood those distinctions.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version