Make RunThreadPlan start the timeout clock for each part of the expression evaluation AFTER the
successful resume for that part.  This will make the timeouts more stable when lldb is running
in a busy program.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206835 91177308-0d34-0410-b5e6-96231b3b80d8
Give the clang functions names.  This is only for logging.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206836 91177308-0d34-0410-b5e6-96231b3b80d8
build: use keyword signatures for link dependencies

This updates the target_link_libraries invocation when building with CMake
2.8.12 or newer.  The newer version of CMake warns when keyword and plain
signatures are used for target_link_libraries.  This addresses that difference
while maintaining compatibility with the older releases by defining a macro for
the keyword that is defined based on the current version of CMake.

Patch originally by chapuni!

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206850 91177308-0d34-0410-b5e6-96231b3b80d8
When increasing the amount of a file read, read the total of the Mach-O header
plus the size of the load commands in case the LC_UUID load command comes near
the end of the file.
<rdar://problem/16599318> 


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206865 91177308-0d34-0410-b5e6-96231b3b80d8
Note that the FreeBSD x86_64 buildbot uses CMake

The other buildbots in the list include their build method.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206892 91177308-0d34-0410-b5e6-96231b3b80d8
Switch to Darwin decorator for tests that XPASS on FreeBSD

Since these tests pass on (at least some) other platforms, change the
decorators to @expectedFailureDwarwin.  Tested on FreeBSD with Clang 3.4
and libc++.

rdar://9980907
rdar://15367233


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206895 91177308-0d34-0410-b5e6-96231b3b80d8
Added a packet-playback test facility for lldb-gdbserver and a few starter tests.

lldbgdbserverutils.py has a new expect_lldb_gdbserver_replay() method
that plays back gdb remote send/receive packets. These packets are the
log lines that come from running the 'log enable gdb-remote packets',
either from the lldb-gdbserver side or the lldb side. There's a flag
to flip which side is the send (lldb-gdbserver input or lldb-gdbserver
output).

This first checkin tests the initial gdbremote handshake, the ability
to turn on the no-ack mode communication style, thread suffix support,
and list threads in stop reply support. The last two are marked xfail
as top of tree does not yet support these.

 --This line, and those below, will be ignored--

M    test/tools/lldb-gdbserver/TestLldbGdbServer.py
M    test/tools/lldb-gdbserver/lldbgdbserverutils.py


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206930 91177308-0d34-0410-b5e6-96231b3b80d8
Windows fix: Need to ensure all APIs are forward decl'd with LLDB_API. If not then frontend linker errors appear due to dllexport differences. There may be some others missing, will commit as I find them.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206958 91177308-0d34-0410-b5e6-96231b3b80d8
Remove duplication in expectedFailure* decorators

Differential Revision: http://reviews.llvm.org/D3452


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206976 91177308-0d34-0410-b5e6-96231b3b80d8
Honour DESTDIR when installing LLDB python module


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@206978 91177308-0d34-0410-b5e6-96231b3b80d8
Fixed a case where if someone added a "bind -v" to their ~/.editrc file, key mappings would get messed up.

I fixed this by only doing el_set(e, EL_BIND, ...) calls before sourcing the .editrc files.

<rdar://problem/16614095>



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@207005 91177308-0d34-0410-b5e6-96231b3b80d8
Change the default key bindings for multi-line mode:
Up/down arrows select next/prev line in multi-line mode
CTRL+N and CTRL+P do next/prev history



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@207033 91177308-0d34-0410-b5e6-96231b3b80d8
Remove the using namespace directives to make it clear where code is scoped.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@207041 91177308-0d34-0410-b5e6-96231b3b80d8
Allow summary formatters to take ValueObjects into account when deciding whether values/children should be printed and if child names should be shown
This decision has always been statically-bound to the individual formatter. With this patch, the idea is that this decision could potentially be dynamic depending on the ValueObject itself



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@207046 91177308-0d34-0410-b5e6-96231b3b80d8
Windows Fix: added inttypes.h. Introduces macro redefinition warnings due to LLVM itself externally defining the PRI macros, but now builds on vs2013.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@207100 91177308-0d34-0410-b5e6-96231b3b80d8
If CMake finds a python interpreter, use it

The FreeBSD package building cluster installs e.g. 'python2.7', but no
plain 'python' to avoid version-related issues.

CMake's FindPythonInterp locates an interpreter with such a name and
provides it in the PYTHON_EXECUTABLE variable.  Use that if it's set,
falling back to the original '/usr/bin/env python' otherwise.

Patch by Brooks Davis in FreeBSD ports commit r352012


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@207122 91177308-0d34-0410-b5e6-96231b3b80d8
Making a SharingPtr out of a nullptr_t should be a safe and allowed operation

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@207129 91177308-0d34-0410-b5e6-96231b3b80d8
Fixed an issue where we would try to interrupt a process while it is in the process of naturally stopping due to another reason (breakpoint, or step).

Added a new MachProcess::Interrupt() which correctly tracks such cases and "does the right thing".

<rdar://problem/16593556>



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@207139 91177308-0d34-0410-b5e6-96231b3b80d8
Fixed a flipped conditional when writing back the
values of variables in the Materializer.

The Materializer should not write the variable
back if its new value is the *same* as the old
value, not if the new value is *different*.

<rdar://problem/16712205>


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@207148 91177308-0d34-0410-b5e6-96231b3b80d8
Fix the build-llvm.pl to use glob to find all llvm and clang .a files for libllvmclang.a.



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