summaryrefslogtreecommitdiffstats
path: root/clang/lib/AST/DeclBase.cpp
diff options
context:
space:
mode:
authorFrancis Ricci <francisjricci@gmail.com>2016-04-27 17:10:15 +0000
committerFrancis Ricci <francisjricci@gmail.com>2016-04-27 17:10:15 +0000
commita030061c5be4d297652a9285b9618a5199600e90 (patch)
treefb3ec799054b2b6f4d8f9c06a6b6829edb5cde55 /clang/lib/AST/DeclBase.cpp
parent9bc3c4f3735edee75dde444e6c7a7bea5e589ed9 (diff)
downloadbcm5719-llvm-a030061c5be4d297652a9285b9618a5199600e90.tar.gz
bcm5719-llvm-a030061c5be4d297652a9285b9618a5199600e90.zip
Use absolute module path when possible if sent in svr4 packets
Summary: If the remote uses svr4 packets to communicate library info, the LoadUnload tests will fail, as lldb only used the basename for modules, causing problems when two modules have the same basename. Using absolute path as sent by the remote will ensure that lldb locates the module from the correct directory when there are overlapping basenames. When debugging a remote process, LoadModuleAtAddress will still fall back to using basename and module_search_paths, so we don't need to worry about using absolute paths in this case. Reviewers: ADodds, jasonmolenda, clayborg, ovyalov Subscribers: lldb-commits, sas Differential Revision: http://reviews.llvm.org/D19557 llvm-svn: 267741
Diffstat (limited to 'clang/lib/AST/DeclBase.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud