Re: [cdt-dev] binary-less debugging

[Thomas Fletcher <thomas@xxxxxxxxxxxxxxxxx>]

John Cortell wrote:
> Having a binary makes plenty of sense for JTAG debugging. There's just 
> different types of launches that one may want.
>
>    - Download, launch and debug an executable
>    - Connect to the target and use the debug information in an 
> executable to provide source level debugging of code already running
>    - Connect without using any debug information--"poke around"
>
> Being able to not specify an executable is desirable for the third 
> scenario and it would be nice if we could get that. I think Ken Ryall 
> looked into it initially and found a lot of dependencies on the binary. 
> He can probably chime in and indicate why he didn't go through with it.

I agree with John.  I run into this frequently with users who are working
with DLL's they've developed but need to create a launch configuration that
includes the core binary (which they often don't have any debug/symbol
information for) just to passify the Launch configuration.

Ideally, if you wanted to debug a DLL, then we'd be able to make a launch
configuration focused on providing that binary component and any additional
bits optionally.  As it is now, you have to include "some" main binary and
then tell the debugger about the DLL, and potentially its source, separately.

+1 for me if it enables/facilitates the creation of a smoother launch 
configuration scenario, assuming all the other entanglements can be removed.

Thomas
--
Thomas Fletcher
Crank Software Inc.
www.cranksoftware.com