Put "jit" in alpha order in log category list


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@202976 91177308-0d34-0410-b5e6-96231b3b80d8
Build JITLoader on FreeBSD also


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@202980 91177308-0d34-0410-b5e6-96231b3b80d8
Add the new JITLoader plugin files to the lldb xcode project file.
Add a cast for a size_t / PRIu64 printf formatter.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203030 91177308-0d34-0410-b5e6-96231b3b80d8
Moved JITLoader.cpp and JITLoaderList.cpp over into "source/Target" since the header files were in "include/lldb/Target".

Also enabled the ELF Core file support in all builds since the header files have been properly separated from ProcessMonitor.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203035 91177308-0d34-0410-b5e6-96231b3b80d8
Temporarily disable the JIT loading detector till we figure out why it crashes when lldb follows through exec's...


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203068 91177308-0d34-0410-b5e6-96231b3b80d8
When a client asks for a queue pending item's extended backtrace,
hold a strong pointer to that extended backtrace thread in the Process
just like we do for asking a thread's extended backtrace.
Also, give extended backtrace threads an invalid ThreadIndexID number.
We'll still give them valid thread_id's.  Clients who want to know the
original thread's IndexID can call GetExtendedBacktraceOriginatingIndexID().
<rdar://problem/16126034> 


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203088 91177308-0d34-0410-b5e6-96231b3b80d8
Fix Windows build break introduced in r203035.

Add '#if defined(__linux__) || defined(__FreeBSD__)' around JITLoaderGDB
and ProcessElfCore, which are only built on Linux and FreeBSD.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203107 91177308-0d34-0410-b5e6-96231b3b80d8
Added lldb-dll-export.h to the public API, fixing
clients of LLDB.

<rdar://problem/16248988>


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203139 91177308-0d34-0410-b5e6-96231b3b80d8
Get rid of lldb-dll-export.h and place the smarts of this into lldb-defines.h. 

Please do not add header files that are required in public APIs without first checking with us. This broke the LLDB builds at Apple because the lldb-dll-export.h wasn't included in the LLDB.framework and it was being included by public API header files.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203177 91177308-0d34-0410-b5e6-96231b3b80d8
Re-enable the JITLoaderGDB and ProcessElfCore that were disabled by:

Author: ace2001ac
Date: Thu Mar  6 05:30:34 2014
New Revision: 203107

URL: http://llvm.org/viewvc/llvm-project?rev=203107&view=rev
Log:
Fix Windows build break introduced in r203035.

Add '#if defined(__linux__) || defined(__FreeBSD__)' around JITLoaderGDB
and ProcessElfCore, which are only built on Linux and FreeBSD.

Modified:
   lldb/trunk/source/lldb.cpp

Windows will need to start building all files necessary so that JITLoaderGDB and ProcessElfCore can build since they should work on all platforms.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203178 91177308-0d34-0410-b5e6-96231b3b80d8
This commit provides support for running the dosep.ty test driver with multiple threads.

It speeds up running the full test suite on my HP z620 Ubuntu machine with 32 hyperthreaded CPUs from 11 minutes to about 1m13s (about 9x).

The default behavior is to run single-threaded as before.  If the environment variable LLDB_TEST_THREADS is set, a Python work queue is set up with that many worker threads.

To avoid collisions within a test directory where multiple tests make use of the same prebuilt executable, the unit of work for the worker threads is a single directory (that is, all tests within a directory are processed in the normal serial way by a single thread).

tfiala & I have run this way a number of times; the only issue I found was that the TestProcessAttach.py test failed once, when attempting to attach to the process "a.out" by name.  I assume this is because some other thread was running an executable of that name at the same time, and we were attempting to attach to the wrong one, so I changed that test to use a different executable name (that change is also included in this commit).


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203180 91177308-0d34-0410-b5e6-96231b3b80d8
Allow line numbers to be shown in multi-line expressions.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203185 91177308-0d34-0410-b5e6-96231b3b80d8
Replace uses of OwningPtr<T> with std::unique_ptr<T>.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203200 91177308-0d34-0410-b5e6-96231b3b80d8
Only enable ProcessElfCore if this is an ELF file.  Right now this plugin is winning over
ProcessMachCore because it doesn't check the format of the file up front.  (this is only now
happening because of Greg's change in r203178 to build ProcessElfCore for non-Linux/FreeBSD
hosts).
<rdar://problem/16257533> 


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203205 91177308-0d34-0410-b5e6-96231b3b80d8
Todd points out that my change to ProcessElfCore is probably
not going to key off of the ELF object file like I'd intended.
Revert my change in r203205; also revert Greg's change in
r203107 which builds ProcessElfCore on non-Linux/FreeBSD systems
for the moment until we can straighten this out.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@203207 91177308-0d34-0410-b5e6-96231b3b80d8
Merge remote-tracking branch 'upstream/master' into warhol-lldb
JITLoader fix based on suggestion from Jim Ingham.