lldb python scripting: unable to show `target.debug-file-search-paths` value using `SBDebugger::GetSetting`

[ZequanWu]

After setting target.debug-file-search-paths on command line, lldb.debugger.GetSetting("target.debug-file-search-paths") is unable to show the value, while it works for target.source-map.

$ lldb
(lldb) settings set target.debug-file-search-paths /tmp/
(lldb) settings set target.source-map /tmp/a/ /tmp/b/
(lldb) script
Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
>>> lldb.debugger.GetSetting("target.debug-file-search-paths")
NULL
>>> lldb.debugger.GetSetting("target.source-map")
[0]:
  [0]: /tmp/a
  [1]: /tmp/b
>>> lldb.debugger.GetSetting("target")
arg0: ""
auto-apply-fixits: True
auto-import-clang-modules: True
auto-install-main-executable: True
auto-source-map-relative: True
breakpoints-use-platform-avoid-list: True
clang-module-search-paths: NULL
debug-file-search-paths: NULL

lldb version is trunk.

[llvmbot]

@llvm/issue-subscribers-lldb

Author: Zequan Wu (ZequanWu)

After setting `target.debug-file-search-paths` on command line, `lldb.debugger.GetSetting("target.debug-file-search-paths")` is unable to show the value, while it works for `target.source-map`.

$ lldb
(lldb) settings set target.debug-file-search-paths /tmp/
(lldb) settings set target.source-map /tmp/a/ /tmp/b/
(lldb) script
Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D.
>>> lldb.debugger.GetSetting("target.debug-file-search-paths")
NULL
>>> lldb.debugger.GetSetting("target.source-map")
[0]:
  [0]: /tmp/a
  [1]: /tmp/b
>>> lldb.debugger.GetSetting("target")
arg0: ""
auto-apply-fixits: True
auto-import-clang-modules: True
auto-install-main-executable: True
auto-source-map-relative: True
breakpoints-use-platform-avoid-list: True
clang-module-search-paths: NULL
debug-file-search-paths: NULL

lldb version is trunk.

[jimingham]

For this to work, each Property type has to implement a ToJSON. PathMap does, but FileSpecList doesn't.

[jimingham]

I kind of dislike that SBDebugger::GetSetting. If you had 5 targets and had given different settings values for each, this would return the CommandInterpreter's currently selected Target's value, which is pretty odd for an SB API.

But that's a whole 'nother issue...