Add object logging to HistoryThread.  Call the DoDestroy() method from
the HistoryThread dtor.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194436 91177308-0d34-0410-b5e6-96231b3b80d8
Add initial --extended / -e support to thread backtrace.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194455 91177308-0d34-0410-b5e6-96231b3b80d8
Future-proof version checking with MSVC_VERSION

This mirrors lld r194481

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194483 91177308-0d34-0410-b5e6-96231b3b80d8
Log failure to restore thread state in ThreadPlanCallFunction::DoTakedown

In order to help track down llvm.org/pr17226.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194487 91177308-0d34-0410-b5e6-96231b3b80d8
Change SBThread::GetExtendedBacktrace to
SBThread::GetExtendedBacktraceThread to make it more clear what is
being returned.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194531 91177308-0d34-0410-b5e6-96231b3b80d8
<rdar://problem/14322677>

Implement a "memory find" command for LLDB

This is still fairly rough around the edges but works well enough for simple scenarios where a chunk of text or a number are to be found within a certain range of memory, as in
mem find `buffer` `buffer+0x1000` -s "me" -c 5 -r



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194544 91177308-0d34-0410-b5e6-96231b3b80d8
Small typos in previous commit

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194546 91177308-0d34-0410-b5e6-96231b3b80d8
Fixed printf warnings. The GetByteSize() results return uint64_t values, not size_t values.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194587 91177308-0d34-0410-b5e6-96231b3b80d8
Minor improvement to the "memory find" command
Remove the --do-read option, and always provide a small dump of memory at each match spot
Add a --dump-offset (-o) option, to specify a byte offset from which to start dumping relative to the matching address

The real solution is to actually provide the format options found on "memory read" and use those as the key to actually printing memory upon each find
That, however, requires a little refactoring work, so put this in for now until I get a chance to do the required shuffling around of moving parts



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194600 91177308-0d34-0410-b5e6-96231b3b80d8
<rdar://problem/15172417>

Added two new GDB server packets to debugserver: "QSaveRegisterState" and "QRestoreRegiterState".

"QSaveRegisterState" makes the remote GDB server save all register values and it returns a save identifier as an unsigned integer. This packet can be used prior to running expressions to save all registers.

All registers can them we later restored with "QRestoreRegiterState:SAVEID" what SAVEID is the integer identifier that was returned from the call to QSaveRegisterState.

Cleaned up redundant code in lldb_private::Thread, lldb_private::ThreadPlanCallFunction.
Moved the lldb_private::Thread::RegisterCheckpoint into its own header file and it is now in the lldb_private namespace. Trimmed down the RegisterCheckpoint class to omit stuff that wasn't used (the stack ID).

Added a few new virtual methods to lldb_private::RegisterContext that allow subclasses to efficiently save/restore register states and changed the RegisterContextGDBRemote to take advantage of these new calls.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194621 91177308-0d34-0410-b5e6-96231b3b80d8
<rdar://problem/14814689>

Add a log message to the console that will display the error code when we fail to reply to a mach message.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194623 91177308-0d34-0410-b5e6-96231b3b80d8
Added documentation or the new QSaveRegisterState and QRestoreRegisterState packets.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194631 91177308-0d34-0410-b5e6-96231b3b80d8
Mark two FreeBSD tests failing due to llvm.org/pr15989

After solving llvm.org/pr17226 these two tests now fail for the same reason
they do on Linux.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194726 91177308-0d34-0410-b5e6-96231b3b80d8
Update failing FreeBSD test annotations (pr17932, pr17933)

After solving the issue in llvm.org/pr17226 these two tests still fail,
now for other reasons.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194729 91177308-0d34-0410-b5e6-96231b3b80d8
Remove annotations for pr17184 (now fixed)

This failure was due to a limitation in the FreeBSD kernel that has now been
addressed.  (llvm.org/pr17226 has the details.)


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194731 91177308-0d34-0410-b5e6-96231b3b80d8
Commit a work-in-progress system runtime for Mac OS X which won't
do anything right now.  Add a few new methods to the Thread base
class which HistoryThread needs.  I think I updated all the 
CMakeLists files correctly for the new plugin.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194756 91177308-0d34-0410-b5e6-96231b3b80d8
Remove the hardcoded declaration to the Python include path. Thanks to Kal Conley for the patch

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194804 91177308-0d34-0410-b5e6-96231b3b80d8
Improve the set of the Python libraries during the cmake build.
Thanks to Kal Conley for the patch




git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194815 91177308-0d34-0410-b5e6-96231b3b80d8
Remove FreeBSD test failure annotations for llvm.org/pr17213

This was a FreeBSD kernel issue, now fixed.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@194842 91177308-0d34-0410-b5e6-96231b3b80d8
test: Remove annotation for now-fixed FreeBSD issue pr15302

The failure to demangle 'anonymous namespace' on FreeBSD is fixed (twice)

- the failure in FreeBSD's in-tree __cxa_demangle has been addressed

- FreeBSD now uses the copy of the demangler built into lldb, due to other
  remaining limitations in the in-tree __cxa_demangle

llvm.org/pr15302


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