Ok, I see. That's really what's needed to solve John's problem, I
believe.
However, as we Nokia & Freescale are still using CDT3.0.2, we miss that
enhancement.
Anyway, John, after we upgrade our CDT to 3.1.1, which is underway, we
will probably see your problem gone.
Thanks.
-- Ling
> -----Original Message-----
> From: cdt-debug-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of ext
> Mikhail Khodjaiants
> Sent: Tuesday, October 03, 2006 11:47 AM
> To: CDT Debug developers list
> Subject: RE: [cdt-debug-dev] source mappings and debugger
>
> Ling,
>
> See the "convertPath" method of CBreakpointManager.
>
> Regards,
> Mikhail
>
> -----Original Message-----
> From: cdt-debug-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of
> Ling.5.Wang@xxxxxxxxx
> Sent: 03 October 2006 17:31
> To: cdt-debug-dev@xxxxxxxxxxx
> Subject: RE: [cdt-debug-dev] source mappings and debugger
>
> Ok, Ken's change is to accommodate need of both our Nokia
> debugger and GDB, namely
> 1) keep my change in CBreakpointManager::setBreakpointsOnTarget0(),
> namely pass full path instead of file name in lineBreakpoint setting.
> 2) move Mikhail's change to MI plugin, namely converting full
> path to file name in MI.
>
> So it does not solve John's problem, I believe.
>
> As to why the marker disappear, it's because in our CDI code
> (John, please look at BreakpointManager::setLineBreakpoint())
> we added code to remove the breakpoint when backend fails to
> set a breakpoint during debug.
>
> As to John's problem, I still think it's likely because wrong
> file path is passed to backend. Anyway, let's see what John
> will discover.
>
> Regards.
>
> -- Ling
>
>
> > -----Original Message-----
> > From: cdt-debug-dev-bounces@xxxxxxxxxxx
> > [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of ext Mikhail
> > Khodjaiants
> > Sent: Tuesday, October 03, 2006 7:48 AM
> > To: CDT Debug developers list
> > Subject: RE: [cdt-debug-dev] source mappings and debugger
> >
> > John,
> >
> > I think it's a different problem. Can you set a breakpoint in the
> > removeBreakpoints() method of
> > org.eclipse.debug.internal.core.BreakpointManager to see
> who calls it?
> >
> > Thanks,
> > Mikhail
> >
> > -----Original Message-----
> > From: cdt-debug-dev-bounces@xxxxxxxxxxx
> > [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of John Cortell
> > Sent: 03 October 2006 11:57
> > To: CDT Debug developers list; CDT Debug developers list
> > Subject: RE: [cdt-debug-dev] source mappings and debugger
> >
> > OK. Now I'm confused again. After the Ling/Ken exchange, I
> walked away
>
> > thinking Ken has some pending CDT and CodeWarrior DE changes (the
> > latter is specific to Nokia and Freescale) that would/could resolve
> > this problem. Ken, can you clarify?
> >
> > At 04:34 AM 10/3/2006, Mikhail Khodjaiants wrote:
> > >Ling,
> > >
> > >As Ken mentioned in his message he has already fix the full
> > path part.
> > >The reverse mapping for the breakpoints has been there too.
> > >As far as I understand the problem is different. The breakpoint's
> > >marker disappears from the editor, which is probably
> > something specific
> >
> > >to the John's implementation.
> > >
> > >Mikhail
> > >
> > >________________________________
> > >
> > >From: cdt-debug-dev-bounces@xxxxxxxxxxx on behalf of
> > >Ling.5.Wang@xxxxxxxxx
> > >Sent: Mon 02/10/2006 8:09 PM
> > >To: cdt-debug-dev@xxxxxxxxxxx
> > >Subject: RE: [cdt-debug-dev] source mappings and debugger
> > >
> > >
> > >
> > >Mikhail, I guess you were talking about a fix in
> > >CBreakpointManager.setBreakpointsOnTarget0() where you just
> > send file
> > >name without path to CDI plugin when setting a
> > lineBreakpoint. But as
> > >your comment in bug 102563 said, it's just a temporary fix:
> > >"Switching back temporary to use file names instead of full
> > paths. Need
> >
> > >to investigate gdb behaviour."
> > >
> > >Actually that fix does cause problem in our cases where same
> > name files
> >
> > >in different paths exist in the workspace.
> > >
> > >John, I reverted Mikhail's fix in our version of
> > CBreakpointManager so
> > >you see your bug. The breakpoint setting fails because the
> > full path
> > >from Eclipse side is not recognized by backend as a file in the
> > >executable.
> > >
> > >A better quick fix, may be to hack in the back end (same
> with GDB),
> > >namely if "full path" is not accepted when setting the
> > breakpoint, try
> > >the file name without path.
> > >
> > >The real solution, I think, may be like this. If source mapping
> > >happens, e.g. original file "originalCompileDir\foo.cpp" is
> > mapped to
> > >"hostSrcDir\foo.cpp", we should pass
> "originalCompileDir\foo.cpp" as
> > >parameter when setting the breakpoint.
> > >
> > >-- Ling
> > >
> > > > -----Original Message-----
> > > > From: cdt-debug-dev-bounces@xxxxxxxxxxx
> > > > [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of
> > ext Mikhail
> > > > Khodjaiants
> > > > Sent: Monday, October 02, 2006 12:10 PM
> > > > To: CDT Debug developers list
> > > > Subject: RE: [cdt-debug-dev] source mappings and debugger
> > > >
> > > > I remember fixing something like that, but I can't
> > remember what was
> >
> > > > the problem. Are you using the latest version with gdb as
> > a backend?
> > > >
> > > > -----Original Message-----
> > > > From: cdt-debug-dev-bounces@xxxxxxxxxxx
> > > > [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of
> > John Cortell
> > > > Sent: 02 October 2006 18:03
> > > > To: CDT Debug developers list; CDT Debug developers list
> > > > Subject: RE: [cdt-debug-dev] source mappings and debugger
> > > >
> > > > I double-click in the editor, in the breakpoint/marker column.
> > > >
> > > > Yes; the file is there, so I realize the file has
> > resolved thanks to
> >
> > > > the source mappings. But the act of setting a breakpoint
> > is what's
> > > > not working correctly.
> > > >
> > > > To make clear the scenario I'm trying: I launch the debug
> > session,
> > > > the app stops at main(), the source shows in the editor
> with the
> > > > instruction pointer at the beginning of main.
> > > > I can step from there.
> > > > However, I try to set a breakpoint further down in
> > main(), and that
> > > > doesn't work, as described earlier (the breakpoint circle
> > shows for
> > > > an instant, but disappears immediately).
> > > >
> > > > John
> > > >
> > > > At 11:56 AM 10/2/2006, Mikhail Khodjaiants wrote:
> > > > >John,
> > > > >
> > > > >How do you set a breakpoint? If you are using the
> > ToggleBreakpoint
> > > > >action in the editor, the source file is already resolved.
> > > > >
> > > > >Thanks,
> > > > >Mikhail
> > > > >
> > > > >-----Original Message-----
> > > > >From: cdt-debug-dev-bounces@xxxxxxxxxxx
> > > > >[mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of John
> > > > >Cortell
> > > > >Sent: 02 October 2006 17:22
> > > > >To: CDT Debug developers list
> > > > >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
> > > > >
> > > > >
> > > > >--
> > > > >The 2006 ARM Developers' Conference, October 3-5, Santa
> > > > Clara, US Join
> > > > >ARM and its technology and tools Partners from around the
> > > > world at the
> > > > >only industry event for developers of ARM Powered(R) solutions.
> > > > >http://www.arm.com/developersconference/
> > > > >
> > > > >
> > > > >IMPORTANT NOTICE: The contents of this email and any
> attachments
> > > > >are confidential and may also be privileged. If you
> are not the
> > > > >intended recipient, please notify the sender immediately
> > and do not
> > > > disclose the
> > > >
> > > > >contents to any other person, use it for any purpose, or
> > > > store or copy
> > > > >the information in any medium. Thank you.
> > > > >
> > > > >
> > > > >_______________________________________________
> > > > >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
> > > >
> > > >
> > > > --
> > > > The 2006 ARM Developers' Conference, October 3-5, Santa
> Clara, US
> > > > Join ARM and its technology and tools Partners from
> > around the world
> >
> > > > at the only industry event for developers of ARM Powered(R)
> > > > solutions.
> > > > http://www.arm.com/developersconference/
> > > >
> > > >
> > > > IMPORTANT NOTICE: The contents of this email and any
> > attachments are
> >
> > > > confidential and may also be privileged. If you are not
> > the intended
> >
> > > > recipient, please notify the sender immediately and do
> > not disclose
> > > > the contents to any other person, use it for any purpose,
> > or store
> > > > or copy the information in any medium. Thank you.
> > > >
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> > >
> > >_______________________________________________
> > >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
> > _______________________________________________
> > 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
> _______________________________________________
> 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
