[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Re: How to set breakpoint in libraries
|
>
> > 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).
>
> First of all: CDT *does* support breakpoint in libraries and it works
> well!
>
> All you have to do is to type in the "break" command from the GDB
> console.
>
> What is missing is the ruler on the right hand side or some other means
> of translating current source file name + line number into a GDB
> command. The source file is opened in Eclipse either via Open External
> file, or via stepping into the file during debugging.
>
Correct.
Breakpoints in Eclipse are tied to IResource/IMarkers. External files
do not have an underlying IResource. The idea is to use a Proxy IResource
to save the information, but if we do this the rest of the components
(CDT/Debug/UI, CEditor, etc ..) must be aware of it.
> Alternative:
>
> How about adding a "set breakpoint on current line" from the
> right-mouse-click menu?=20
>
As you pointed you can use the GDB console, (for other alternatives see the
previous email). But it does not provide persistency and other Eclipse/UI features.
