[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Removing "stdout/stdin/stderr" console for embedded development
|
>
> I ended up removing this console entirely for my "idle" debug mode. It
> doesn't make any sense(in its current form) for embedded development.
>
> Embedded CDT debugging is *really* shaping up!=20
>
> http://zylin.com/pipermail/zylin-discuss_zylin.com/2004-October/000048.html
>
> My changes to CDT are basically:
>
> - add CygWin -> Windows path translation in various places.=20
This was ... problematic.
Your proposed patch was not apply because it puts
Cygwin specifics all over the CDT.
> - Add an "idle" debug mode. This allows launching the GDB debugger in
> "idle" mode. That is before GDB is connected to a target, without
> specifying an executable, before symbols are loaded, etc. All
> connection, loading of symboles, etc. is done manually via GDB
> console(or .gdbinit files). Since a lot of nasty, target specific stuff
> needs to happen here(e.g. erasing application from flash, writing the
> new application to flash, reseting the target, etc.) it doesn't make
> much sense to try to squeeze this into a standard GUI.
>
So if I read you correctly, beside the 3 other launch(s), we have currently in CDT(head)
+ C/C++ post-mortem debugger
+ C/C++ attach to local application
+ C/C++ local application (*)
(*) this one includes the GDBServer.
You want an idle launch
+ C/C++ idle debugger (GDB)
Only starts the debugger and waits idle ... ok.
Although I did not do such launch, I do not see what modifications you
required to make this possible in your own plugin, it should be straight forward(sic).
Something I'm missing?
- Using .gdbinit
Was it not possible to stuff you extra commands in "gdbinit" and use the
"C/C++ local aplication" launch ? Why do you need to start only gdb ?
