debugger options tied to configure options - wish

Vladimir Prus ghost at cs.msu.su
Sun Feb 3 10:23:45 UTC 2008


On Sunday 03 February 2008 09:35:37 kitts wrote:
> In my recent experience with developing for embedded systems using the 
> KDevelop IDE i felt the need for debugger options to be tied to configure 
> options (or any other build manager). Let me explain...
> 
> When developing for embedded systems typically apart from the usual debug and 
> release build, there are debug for ram and debug for flash. ie. the code may 
> be executed in RAM or in ROM and the linker script is differrent in each 
> case.
> Second, we typically use a gdbinit script and this script is again differrent 
> for RAM and ROM (where it first needs to program the flash before starting 
> execution)

You really should be using current version of GDB together with remote
stub that supports flash write -- in which case it will be totally transparent 
for you;-)

> I currently use the cmake build system (the lack of a cmake plugin requires me 
> to manually reconfigure the build) and i can switch the linker scripts but i 
> also need to edit project options to use the other gdbinit.
> 
> So, would it be possible to link the debugger settings with the build system 
> settings, assuming that the cmake plugin in future will allow to have 
> multiple build folders/settings similar to the automake plugin.

The current (vague) plan is to have 'debugger configuration' thing, where the 'application'
can be either binary, or a target in the build system. In the latter case, it would
be reasonable to grab as much data as possible from the build system. OTOH,
I'm not quite sure that "ROM/RAM" option is a standard thing in any build system
nowdays. Probably, we can use Python scripting to do different thing depending on
the linker script used by the target being debugged.

- Volodya








More information about the KDevelop mailing list