[cdt-debug-dev] Projectless development

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

> What kind of commands were you thinking of? 

If I have an executeable, e.g. foo.elf compiled with an ARM toolchain, I
would type something like:

arm-elf-gdb -w foo.elf

to start an Insight debug session.

I would like to be able to do the same w/CDT.

cdt --target=arm-elf foo.elf

Launches a CDT debug session. I think DDD requires me to specify target
whereas with arm-elf-gdb it is implied. 

Various useful options/functions(not thought out, just what pops into
mind):

- Passthrough of options to GDB. "--gdb=--foo,bar" => passthrough of the
  "--foo bar" option to GDB launched by CDT. Syntax borrowed from
  GCC -Wl,xxx.
- "cdt" command should be responsible for launching GDB such that
  GDB gets the same environment as the "cdt" command.
- CDT should be capable of dealing with "idle" mode where the
  executable to be debugged is loaded via the GDB command line console.


> Does it need to communicate to a currently running instance of CDT? Or did
> you just want to run a command that starts a debug session (kind of like ddd)?

I guess I don't care. If the "cdt" command above needs a running
instance of Eclipse + CDT, then that's fine. If it can launch Eclipse +
CDT if it isn't already running, fine, but not big deal.

> There have been a few requests to support project-less debug. I wonder if a
> good approach would be to create an RCP-based client that includes
> everything you need to do this but without the need for magic
> workspaces/projects.

What's RCP? Java remote procedure calls? 

Sounds like you are onto the right track though. :-)

> I would hope that the cdt debug plug-ins could be used
> in such an environment. I wonder how much work that would be...

-- 
Øyvind Harboe
http://www.zylin.com