aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h
diff options
context:
space:
mode:
authorTom Yang <zhenyutyang@gmail.com>2023-10-21 16:59:44 -0700
committerGitHub <noreply@github.com>2023-10-21 16:59:44 -0700
commit74ca07295f3224a77ea5202858b3f4195b23fbcf (patch)
tree38e5c252724eb1b8760608e293447033ae2642e4 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h
parent6250afe37fd1f7d9fecf18e3cfdadf638a299c8a (diff)
downloadllvm-74ca07295f3224a77ea5202858b3f4195b23fbcf.zip
llvm-74ca07295f3224a77ea5202858b3f4195b23fbcf.tar.gz
llvm-74ca07295f3224a77ea5202858b3f4195b23fbcf.tar.bz2
[lldb] improve dwo path in missing dwo error when relative (#69783)
When the debug info refers to a dwo with relative `DW_AT_comp_dir` and `DW_AT_dwo_name`, we only print the `DW_AT_comp_dir` in our error message if we can't find it. This often isn't very helpful, especially when the `DW_AT_comp_dir` is ".": ``` (lldb) fr v error: unable to locate .dwo debug file "." for skeleton DIE 0x000000000000003c ``` I'm updating the error message to include both `DW_AT_comp_dir` (if it exists) and `DW_AT_dwo_name` when the `DW_AT_dwo_name` is relative. The behavior when `DW_AT_dwo_name` is absolute should be the same.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.h')
0 files changed, 0 insertions, 0 deletions