Host: unconstify editline paramters

Although the interface to el_push should be a constant parameter (as it is on
Darwin), certain Linux distributions currently ship a header which does not
provide proper const correctness.  This causes compilation failures on Linux.
Strip the constness on the parameter, which whilst incorrect, is mostly
harmless.  The parameter will not be changed by the interface and so it is
acceptable to do this.  When distributions have updated to a more correct
declaration, it would be nice to revert this change.

Addresses PR18784.

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

Made sure we pass along the file action paths for stdin/stdout/stderr to the XPC service.
[Reviewed by Greg Clayton]


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201103 91177308-0d34-0410-b5e6-96231b3b80d8
Adjust the calls to __introspection_dispatch_thread_get_item_info to
use a system-wide unique thread ID instead of a pthread_t to identify
the thread we want debug info for.  Also, free some more memory regions
that needed to be freed.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201117 91177308-0d34-0410-b5e6-96231b3b80d8
Change RNBRemote::HandlePacket_m() to store the packet on the heap
instead of on the stack.  Handles larger packet read requests better.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201118 91177308-0d34-0410-b5e6-96231b3b80d8
Add decorator for llvm.org/pr18805 until root cause is identified


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201153 91177308-0d34-0410-b5e6-96231b3b80d8
Don’t leak memory when reading memory and we do an early return for error conditions.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201164 91177308-0d34-0410-b5e6-96231b3b80d8
Update decorator for FreeBSD failure pr18066

The test expects the inferior to have exited, but it is still stopped.

llvm.org/pr18066


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201166 91177308-0d34-0410-b5e6-96231b3b80d8
Remove decorators for llvm.org/pr17920 fixed by r200646


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201167 91177308-0d34-0410-b5e6-96231b3b80d8
Remove FreeBSD decorator for llvm.org/pr17499 (no longer fails)


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201168 91177308-0d34-0410-b5e6-96231b3b80d8
Remove decorator for llvm.org/pr17233

This test was skipped as it used to segfault on FreeBSD.  It seems
the original issue has since been fixed, so have the test run again.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201169 91177308-0d34-0410-b5e6-96231b3b80d8
When a multiline expression produces output, the multi-line help message is printed twice.

<rdar://problem/16031890> 



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201171 91177308-0d34-0410-b5e6-96231b3b80d8
Fix cmake compilation on Mac OS X.

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201200 91177308-0d34-0410-b5e6-96231b3b80d8
Avoid leaking namebuf in case of an early exit

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201206 91177308-0d34-0410-b5e6-96231b3b80d8
Fix elf core file VMA-contiguous region collapsing.

Elf core files were collapsing core segments when the virtual memory
addresses were contiguous without checking if the core-file-backed
memory region was the same size as the segment's VMA region. Without
this extra check, any time regions were collapsed but the core-backed
region was smaller (and thus had a zero-filled hole at the end), the
collapse operation would break VMA to core file lookups for subsequent
collapsed regions.

This change fixes the following bug:
http://llvm.org/bugs/show_bug.cgi?id=18769



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201214 91177308-0d34-0410-b5e6-96231b3b80d8
Change TestAbbreviations test to expected failure on Linux.

See http://llvm.org/bugs/show_bug.cgi?id=18816.
Likely the same issue as http://llvm.org/bugs/show_bug.cgi?id=18805.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201244 91177308-0d34-0410-b5e6-96231b3b80d8
Add support for DW_OP_piece and DW_OP_bit_piece.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201268 91177308-0d34-0410-b5e6-96231b3b80d8
Fixed the functionalities/abbreviation/TestAbbreviations.py test case.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201270 91177308-0d34-0410-b5e6-96231b3b80d8
Fixed the TestLogging test.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201273 91177308-0d34-0410-b5e6-96231b3b80d8
Remove decorator for fixed test

llvm.org/pr18805 fixed by r201270


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@201284 91177308-0d34-0410-b5e6-96231b3b80d8
Change the ABI CallFrameAddressIsValid methods for i386 and x86_64.
They were enforcing 16-byte alignment on stack frames for Darwin x86 programs.
But we've found that trap handlers typically don't have the stack pointer
aligned correctly when a trap happens and lldb wasn't backtracing all
the way through.  This method is only used as a safety guard to prevent
lldb's unwinder from using a bogus address as a stack frame - we'll still
enforce word-size alignment on stack frames so that should be fine.

Also rolled back akaylor's changes from August 2013 in r188952 which changed
the i386 ABI plugin to relax the CallFrameAddressIsValid offsets for non-Darwin
targets where only 4-byte alignment is enforced.  Now Darwin is the same as
those environments.

<rdar://problem/15982682> 


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