[cdt-debug-dev] source mappings and debugger

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-debug-dev] source mappings and debugger

From: John Cortell <john.cortell@xxxxxxxxxxxxx>
Date: Mon, 02 Oct 2006 11:22:17 -0500
Delivered-to: cdt-debug-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/cdt-debug-dev>
List-help: <mailto:cdt-debug-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>, <mailto:cdt-debug-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>, <mailto:cdt-debug-dev-request@eclipse.org?subject=unsubscribe>

When using the source-mapping feature in a CDT debug launchconfiguration when the absolute paths in the debug information of anexecutable don't match the sources on the host machine (where Eclipseis running), we're seeing that one cannot set breakpoints in thesource during a debug session. Is this a known limitation?


The source files are outside the workspace.

John

Follow-Ups:
- Re: [cdt-debug-dev] source mappings and debugger
  - From: Pawel Piech
- Re: [cdt-debug-dev] source mappings and debugger
  - From: Ken Ryall

References:
- Re: [cdt-debug-dev] Debugging multiple core microcontrollers.
  - From: Mikhail Khodjaiants

Prev by Date: RE: [cdt-debug-dev] Debugging Qt types in Eclipse
Next by Date: Re: [cdt-debug-dev] source mappings and debugger
Previous by thread: Re: [cdt-debug-dev] Debugging multiple core microcontrollers.
Next by thread: Re: [cdt-debug-dev] source mappings and debugger
Index(es):
- Date
- Thread

Breadcrumbs