mirror of
https://github.com/intel/llvm.git
synced 2026-01-22 23:49:22 +08:00
Document the DBGSourcePathRemapping dictionary that may be
present in the dSYM per-uuid plist, its precedence order with the older DBGBuildSourcePath/DBGSourcePath, and note that must be present and have a value of 3 or the dictionary will be ignored. <rdar://problem/46421686> llvm-svn: 349409
This commit is contained in:
@@ -262,6 +262,17 @@ A40597AA-5529-3337-8C09-D8A014EB1578.plist
|
||||
<string>/path/to/foo.dSYM/Contents/Resources/DWARF/foo</string>
|
||||
<key>DBGSymbolRichExecutable</key>
|
||||
<string>/path/to/unstripped/executable</string>
|
||||
<key>DBGVersion</key>
|
||||
<string>3</string>
|
||||
<key>DBGSourcePathRemapping</key>
|
||||
<dict>
|
||||
<key>/path/to/build/time/src/location1</key>
|
||||
<string>/path/to/debug/time/src/location</string>
|
||||
<key>/path/to/build/time/src/location2</key>
|
||||
<string>/path/to/debug/time/src/location</string>
|
||||
</dict>
|
||||
<key>DBGSymbolRichExecutable</key>
|
||||
<string>/path/to/unstripped/executable</string>
|
||||
</dict>
|
||||
</plist>
|
||||
</tt></pre></code>
|
||||
@@ -271,6 +282,22 @@ so making the results of your shell script will be very easy to create by
|
||||
combining two plists into a single one where you take the UUID and use it a
|
||||
string key, and the value is the contents of the plist.
|
||||
|
||||
<p>LLDB will read the following entries from the per-UUID plist file in the dSYM
|
||||
bundle: <b>DBGSymbolRichExecutable</b>, <b>DBGBuildSourcePath</b> and
|
||||
<b>DBGSourcePath</b>, and <b>DBGSourcePathRemapping</b> if <b>DBGVersion</b> is 3
|
||||
or higher. <b>DBGBuildSourcePath</b> and <b>DBGSourcePath</b> are for remapping
|
||||
a single file path. For instance, the files may be in /BuildDir/SheetApp/SheetApp-37
|
||||
when built, but they are in /SourceDir/SheetApp/SheetApp-37 at debug time, those
|
||||
two paths could be listed in those keys. If there are multiple source path
|
||||
remappings, the <b>DBGSourcePathRemapping</b> dictionary can be used, where an
|
||||
arbitrary number of entries may be present. <b>DBGVersion</b> should be 3 or
|
||||
<b>DBGSourcePathRemapping</b> will not be read. If both <b>DBGSourcePathRemapping</b>
|
||||
AND <b>DBGBuildSourcePath</b>/<b>DBGSourcePath</b> are present in the plist, the
|
||||
<b>DBGSourcePathRemapping</b> entries will be used for path remapping first. This
|
||||
may allow for more specific remappings in the <b>DBGSourcePathRemapping</b>
|
||||
dictionary and a less specific remapping in the
|
||||
<b>DBGBuildSourcePath</b>/<b>DBGSourcePath</b> pair as a last resort.
|
||||
|
||||
|
||||
</div>
|
||||
<div class="postfooter"></div>
|
||||
|
||||
Reference in New Issue
Block a user