# Edit Source Lookup Path Mappings

Use the Source Lookup Path Mappings to edit the Path Mapping source container type.

Source Lookup Path Mappings Options
Options | Description
--- | ---
Name | The name of the Path Mapping. Only the name "Found Mappings" is used by CDT when automatically creating path mappings, such as from the C Source Not Found Editor.

Compilation path:

The path of the folder as it is in the debug information. This is the folder path when the source was compiled.

This path must exactly match the path as it is in the debug information. For example, if a file was compiled with forward (/) slashes, then forward slashes should be entered as path separator. Similarly, if there is a relative path (such as "..") in the compilation path, that should be included as well.

The C Source Not Found Editor automatically creates the correct form when "Locate File..." is used.

Local file system path: | The path of the folder as it is locally, where Eclipse can find the file.
Resolve path mappings using debugger backend. | Allow the mapping to be performed with the debugger backend where supported. This allows any direct interaction with the backend (for example via the console) to have a consistent view of file names. This option is the default and provides a more complete path mapping solution.
Add | Add a new row to the table. Both the Compilation path and Local file system path need to be specified.
Remove | Remove the currently selected row.
Up | Move the currently selected row higher in the list.
Down | Move the currently selected row lower in the list.