Always print the kernel UUID and load address if we are working with
a kernel binary - even if we can't find the symbol-rich binary or 
dSYM on the debugger-system.  Print a warning if the symbol-rich binary
cannot be located.  This more closely emulates the gdb behavior when
a kernel debug session failed to locate a kernel binary.

<rdar://problem/13016095> 


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@175491 91177308-0d34-0410-b5e6-96231b3b80d8
Experiment with printing a warning message when lldb is unable to
find a binary on the debugger-host during a kernel debug session
for a kernel extension (kext).  This may prove to be too verbose
in typical usage, particularly if there are many third-party kexts.
We'll try this and see how it works.

<rdar://problem/13080833> 


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@175494 91177308-0d34-0410-b5e6-96231b3b80d8