Re: [cdt-debug-dev] CDT & RCP

["Mikhail Khodjaiants" <mikhailk@xxxxxxx>]

> What's wrong with parsing the ELF file and trawling out debug
> information? We can find the
> sources and offer them rather than making the user do repetetive labour.

Nothing wrong with it, but we need support for various debug formats.

> Even after start, can you set line breakpoints on files not in projects?
> How do you
> browse? IIRC, files outside the workspace are missing the breakpoint
> margin. We added a
> "break on function/address" menu item because I couldn't find one in the
> standard cdt.

In CDT 3.0 you can set breakpoints on the files outside the workspace. To 
browse use "File"->"Open File" menu which is available in Eclipse 3.1.

----- Original Message ----- 
From: "Pete MacLiesh" <pmac@xxxxxxxxxxxxx>
To: "'CDT Debug developers list'" <cdt-debug-dev@xxxxxxxxxxx>
Sent: Thursday, November 17, 2005 12:01 PM
Subject: RE: [cdt-debug-dev] CDT & RCP


> comments inline
>
> > -----Original Message-----
> > From: cdt-debug-dev-bounces@xxxxxxxxxxx
> > [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of
> > Mikhail Khodjaiants
> > Sent: Tuesday, November 15, 2005 1:40 PM
> > To: CDT Debug developers list
> > Subject: Re: [cdt-debug-dev] CDT & RCP
> >
> > >- try to remove the requirement that a debug session
> > requires a project.
> > >  Perhaps by implementing an EmptyProject class.
> >
> > I see at least two problems:
>
> > 1. Assuming the executable is not built with full paths, the
> > user has to
> > setup the source lookup path for each session.
>
> What's wrong with parsing the ELF file and trawling out debug
> information? We can find the
> sources and offer them rather than making the user do repetetive labour.
>
> > 2. There is no way to set a breakpoint before the session.
>
> Even after start, can you set line breakpoints on files not in projects?
> How do you
> browse? IIRC, files outside the workspace are missing the breakpoint
> margin. We added a
> "break on function/address" menu item because I couldn't find one in the
> standard cdt.
>
>
>
> Is the challenge really "projectless debugging" or maybe just "minimum
> setup / overhead
> debugging"?
>
>
>
> We (Tensilica) built a trivial executable launcher that provides a bunch
> of command line
> args to eclipse.
>
> Then an IStartup listener
>
> - processes the args
> - trawls the binary for files
>  ... and creates a project for free with a linked
>  folder for each of the interesting folders
>  (has source) in the binary.
> - creates a launch
>
> We switched the debug perspective to show the c/c++ projects view
> instead of the outline
> ... and voila ... users can browse the source of the image, everything
> that can be found
> is in a project for line breakpoints and things. Also they can terminate
> and hit F11 to
> debug again because of the launch. They can even use the editor to make
> source changes and
> then go outside to type make if that's what hits their button.
>
> How this could become usable for non-Elf and non-gdb based launches I
> don't know ...
>
>
> Ciao,
>
> PMac
>
> -----------------------------------------------------------
> Pete MacLiesh                      email pmac@xxxxxxxxxxxxx
> Tensilica, Inc.                          tel.  408-327-7327
>                                         fax   408-986-8919
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev