aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp
diff options
context:
space:
mode:
authorJason Molenda <jmolenda@apple.com>2016-07-29 06:24:03 +0000
committerJason Molenda <jmolenda@apple.com>2016-07-29 06:24:03 +0000
commit8129255e7637b195981a21fcba93a7af0dbdb4a1 (patch)
treede87993354f2443952550b04e04c64d20777c0a6 /lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp
parented94271350b2e9c846954de58802a8e6893eb479 (diff)
downloadllvm-8129255e7637b195981a21fcba93a7af0dbdb4a1.zip
llvm-8129255e7637b195981a21fcba93a7af0dbdb4a1.tar.gz
llvm-8129255e7637b195981a21fcba93a7af0dbdb4a1.tar.bz2
PlatformDarwinKernel maintains a list of kexts and kernels
that it finds on the local computer in "well known" locations when we start up the darwin-kernel platform. It did not distinguish between kexts/kernels with dSYMs from others - when it needed a kernel/kext with a given UUID, it would grab the first one it finds. This change separates these into two vectors -- a collection of kexts and kernels with dSYMs next t othem, and a collection of kexts and kernels without dSYMs. When we have a bundle ID and uuid to search for, we first try the collections with dSYMs, and if that fails, then we try the collections that did not have dSYMs next to them. Often times we'll have a situation where a kext will be installed in multiple locations on a system, but only one of them will have a dSYM next to it, where the dev just copied it to a local directory. This fixes that problem, giving precedence to those binaries with debug information. llvm-svn: 277123
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteClientBase.cpp')
0 files changed, 0 insertions, 0 deletions