Re: [cdt-debug-dev] How to set breakpoint in libraries

["Alain Magloire" <alain@xxxxxxx>]

> 
> Hi,
> 
> I'm also very interested in getting this issue solved once and for all. 
> This is really a huge show stopper for using CDT in real life projects.
> 

First there are workarounds:

- bring the library source into the workspace (as an other project, a link etc ..)

- On the property "C/C++ Make project" you can add libraries that the
  model should consider part of the project, for example /usr/lib/debug/libsocket.so
  This will appear in the C/C++ project view and you then could breakpoints
  in the outliner/tree of the this virtual file.

> Is there a way to wrap external files as IResources so they have 
> IMarkers?

No.

> If so, should this be done in the CDT or in 
> org.eclipse.debug.core?
> 

We were planning to do something in the same line as the JDT, where
you associate a source folder(*.jar, *.zip, etc..) to a library and
markers are provided with a uniq handle on the project or the zip file.
We probably have to go a step further and provide IMarkers(redirected to
say the project) for external headers(in C++ the method maybe inline).

This is all and good, but it takes time and I do not see this for 2.1,
probably for 3.x.

Of course, you are more then welcome to jump in and help.

> Øyvind Harboe wrote:
> 
> >Does anyone have any tips on how to modify CDT to make the ruler on the
> >right hand side of the source view appear for files which are not part
> >of the CDT project?
> >
> >Some source files to look at, which source files to glean at?
> >
> >I'd like to have the ability to set breakpoints in e.g. C++ STL
> >libraries, eCos, etc. whose source files are not part of the CDT
> >project.
> >

This is slightly different, the source, for C++ STL, is somethimes
in the header itself (inline) as oppose to say libsocket.so where the
source is under /tmp/debug/libsocket/src.

But yes, I agree, it would be nice.