gdb-remote signal delivery test cleanup.

Learned that MacOSX only accepts signal delivery on a thread that is
already signal handling.  Reworked the test exe to cause a SIGSEGV
and recover if either nothing intercepts the SIGSEGV handler, or
if a SIGUSR1 is inserted.  The test uses the latter part to test
signal delivery on continue using the SIGUSR1.

I still don't have this working on MacOSX.  I'm seeing the
signal get delivered to a different thread than the one I'm
specifying with $Hc{thread-id} + $C{signo}, or with
$vCont;C{signo}:{thread-id};c.  I'll come back to this
after getting it working on the llgs branch on Linux x86_64.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@209912 91177308-0d34-0410-b5e6-96231b3b80d8
Don't use libc's "char *basename(char *)" or "char *dirname(char *)" as they are not thread safe.

I switched the lldb_private::FileSpec code over to use "llvm::StringRef llvm::sys::path::filename(llvm::StringRef)" for basename() and "llvm::StringRef llvm::sys::path::parent_path(llvm::StringRef)" for dirname().

<rdar://problem/16870083>


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@209917 91177308-0d34-0410-b5e6-96231b3b80d8
Fix most of the remaining Windows build warnings.

See http://reviews.llvm.org/D3944 for more details.

Change by Zachary Turner.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@210035 91177308-0d34-0410-b5e6-96231b3b80d8
Add executable extension to debugger name, run dotest via binary.

See http://reviews.llvm.org/D3904 for details.

Change by Scott Graham.



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