Re: [cdt-dev] binary-less debugging

[Elena Laskavaia <ELaskavaia@xxxxxxx>]

I was referring to "poke around", which is simply not possible now 
because it requires binary (unless you provide some fake binary).


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.
>
> John
>
> At 09:53 AM 5/2/2008, Elena Laskavaia wrote:
> >I want to fix CDI launch (CDIDebugModel.newDebugTarget) to make binary
> >argument optional (i.e. null possible),
> >because passing debugging binary for many cases does not make any sense
> >- such as for JTag debugging.
> >In this case it launch gdb without binary argument, and set-up can use
> >gdb commands to set symbol file, etc.
> >
> >It does not mean that it would be optional in UI, default debug launch
> >still requires it.
> >
> >Any objections?
> >_______________________________________________
> >cdt-dev mailing list
> >cdt-dev@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>