Re: [cdt-debug-dev] source mappings and debugger

[John Cortell <john.cortell@xxxxxxxxxxxxx>]

CBreakpointManager.isTargetBreakpoint does get hit.

The breakpoint circle appears for a very brief instant then 
disappears. You can barely see it, it happens so fast; but it's clear 
it's being set then cleared immediately.

The debug information has absolute paths to the source.

John

At 11:34 AM 10/2/2006, Ken Ryall wrote:
> John,
>
> I've done some work with the source locators so they will work better with
> files with absolute paths and that may help. I was waiting for 3.1.1 to go
> out before committing this for 3.1.2, I'll try to get it in this week.
>
> Where does the breakpoint setting fail? Does it make it to
> CBreakpointManager.isTargetBreakpoint?
>
> - Ken
>
> > From: ext John Cortell <john.cortell@xxxxxxxxxxxxx>
> > Reply-To: CDT Debug developers list <cdt-debug-dev@xxxxxxxxxxx>
> > Date: Mon, 02 Oct 2006 11:22:17 -0500
> > To: CDT Debug developers list <cdt-debug-dev@xxxxxxxxxxx>
> > Subject: [cdt-debug-dev] source mappings and debugger
> >
> > When using the source-mapping feature in a CDT debug launch
> > configuration when the absolute paths in the debug information of an
> > executable don't match the sources on the host machine (where Eclipse
> > is running), we're seeing that one cannot set breakpoints in the
> > source during a debug session. Is this a known limitation?
> >
> > The source files are outside the workspace.
> >
> > John
> >
> > _______________________________________________
> > cdt-debug-dev mailing list
> > cdt-debug-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
>
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev