)]}' { "commit": "fb5dd98ff1a76c7fb2b34dad06e8dc2e14fc6b52", "tree": "7e26a03fa945a0d3f55eaac41b5a12d7619fb8fd", "parents": [ "108c616fd1d13c7d6871f22142af0975c8892589" ], "author": { "name": "Caroline Tice", "email": "cmtice@google.com", "time": "Fri Apr 16 11:06:19 2021 -0700" }, "committer": { "name": "Copybara-Service", "email": "copybara-worker@google.com", "time": "Fri Apr 16 12:27:25 2021 -0700" }, "message": "[LLDB] Re-land: Use path relative to binary for finding .dwo files.\n\nDWARF allows .dwo file paths to be relative rather than absolute. When\nthey are relative, DWARF uses DW_AT_comp_dir to find the .dwo\nfile. DW_AT_comp_dir can also be relative, making the entire search\npatch for the .dwo file relative. In this case, LLDB currently\nsearches relative to its current working directory, i.e. the directory\nfrom which the debugger was launched. This is not right, as the\ncompiler, which generated the relative paths, can have no idea where\nthe debugger will be launched. The correct thing is to search relative\nto the location of the executable binary. That is what this patch\ndoes.\n\nDifferential Revision: https://reviews.llvm.org/D97786\n\nGitOrigin-RevId: 3dc24bc31edbc01dea085b24a6a6b024d7ae531c\n", "tree_diff": [ { "type": "modify", "old_id": "3a04f429c7c75a6b0a2ac33dd01fc6ffb7eb28ff", "old_mode": 33188, "old_path": "source/Plugins/SymbolFile/DWARF/SymbolFileDWARF.cpp", "new_id": "da170383405fb5217ec4415d490155e1ef525fb1", "new_mode": 33188, "new_path": "source/Plugins/SymbolFile/DWARF/SymbolFileDWARF.cpp" }, { "type": "add", "old_id": "0000000000000000000000000000000000000000", "old_mode": 0, "old_path": "/dev/null", "new_id": "1916461e3ce8b45d6acb5f21e962e5acbbc0532e", "new_mode": 33188, "new_path": "test/Shell/SymbolFile/DWARF/dwo-relative-path.s" } ] }