[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-debug-dev] StandAlone CDT debugger (was: Debugging native apps)
|
> Two of the more common use cases that we do have today for our (non-Eclipse) Code Compose Studio product are:
> (1) Connect to target, browse to, load and run target executable (perhaps debug)
> (2) (Program in Flash memory) Connect to target, browse to executable/symbol file, load symbols, run target executable (perhaps debug)
>
>Both are very valid with or without the presence of a project or source files. This is not unique to our product as I have often used windbg or DevStudio to simply load up and debug an application without the sources when I come across a crash.
>
>Like Chris says, currently this usage pattern is very clumsy in Eclipse in general with the requirement being that the resources have to be in (somehow) in the workspace. I'm not yet sure how we're going to address this but our users are definitely going to come across this when we start enabling CCE for more complex processors which will have much more complex projects that are built in custom environments.,
>
>Anyway I suspect that this may be a very common usage pattern for embedded tool vendors - I hope a number of us can get together at EclipseCon and discuss this and other related topics.
Our existing MFC-IDE is also somehow different to Eclipse. It's also a full IDE with
project management and build tool chain, class browser etc. But it always connects
to the target. There is no distinction between "Development" and "Debug". You can
also change and reload some stuff on the fly (though not C-Code). When I tried to
accomplish this with Eclipse I was in "Debug" most of the time, even while writing
code. But "Debug" obviously is not the best for developing. So if there was a simpler,
more "disconnected" debug mechanism it might be easier for us to reach our goal.
But then again we're still halted with gdb which also doesn't stand up to our needs
yet (continuously running independent threads/processes).
bye Fabi
