diff options
| author | Ramkumar Ramachandra <artagnon@gmail.com> | 2015-11-12 14:44:24 +0000 |
|---|---|---|
| committer | Ramkumar Ramachandra <artagnon@gmail.com> | 2015-11-12 14:44:24 +0000 |
| commit | 314b7525134730b500a5f1c09e94416676221b31 (patch) | |
| tree | 0ac8cb91d4d60d4d292351a36022981e77b1c6b3 /lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp | |
| parent | 7384a2de027b5b5b20b5110b64d05bbe51ea3a03 (diff) | |
| download | bcm5719-llvm-314b7525134730b500a5f1c09e94416676221b31.tar.gz bcm5719-llvm-314b7525134730b500a5f1c09e94416676221b31.zip | |
Use uniqueness of C++ fully-qualified names to resolve conflicts
A very expected layout: source tree is in ~/src/llvm, the build directory is in
~/src/llvm-build, and the install location is in /usr/local/{lib,include}.
The DWARF information in /usr/local/lib/libLLVM.a for ilist.h points to
~/src/llvm-build/include/llvm/ADT/ilist.h. Now, when someone includes
"llvm/ADT/ilist.h" and links against /usr/local/lib/libLLVM.a. Disaster.
The DWARF information in libUser.so for ilist.h points to two locations: the one
in /usr/include, and the one in ~/src/llvm-build/include. LLDB gets confused.
Let's uniquify fully-qualified names and never trip on such a thing.
Differential Revision: http://reviews.llvm.org/D14549
llvm-svn: 252898
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonDataObjects.cpp')
0 files changed, 0 insertions, 0 deletions
