Fix the copy constructor and assignement operator for the lldb_private::Value class to "do the right thing".



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@209036 91177308-0d34-0410-b5e6-96231b3b80d8
Update how we create our MCSymbolizer to keep working correctly
on arm64 binaries after the llvm r206063 changes.  
Patch written by Jim Ingham and Lang Hames.
<rdar://problem/16935671> 


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@209051 91177308-0d34-0410-b5e6-96231b3b80d8
Introduce the concept of a "display name" for types

Rationale:
Pretty simply, the idea is that sometimes type names are way too long and contain way too many details for the average developer to care about. For instance, a plain ol' vector of int might be shown as
std::__1::vector<int, std::__1::allocator<....
rather than the much simpler std::vector<int> form, which is what most developers would actually type in their code

Proposed solution:
Introduce a notion of "display name" and a corresponding API GetDisplayTypeName() to return such a crafted for visual representation type name
Obviously, the display name and the fully qualified (or "true") name are not necessarily the same - that's the whole point
LLDB could choose to pick the "display name" as its one true notion of a type name, and if somebody really needs the fully qualified version of it, let them deal with the problem
Or, LLDB could rename what it currently calls the "type name" to be the "display name", and add new APIs for the fully qualified name, making the display name the default choice

The choice that I am making here is that the type name will keep meaning the same, and people who want a type name suited for display will explicitly ask for one
It is the less risky/disruptive choice - and it should eventually make it fairly obvious when someone is asking for the wrong type

Caveats:
- for now, GetDisplayTypeName() == GetTypeName(), there is no logic to produce customized display type names yet.
- while the fully-qualified type name is still the main key to the kingdom of data formatters, if we start showing custom names to people, those should match formatters



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@209072 91177308-0d34-0410-b5e6-96231b3b80d8
Add support for gdb remote $X stop notification.

debugserver now returns $X09 as the immediate response to
a $k kill process request rather than $W09.

ProcessGDBRemote now properly handles X as indication of
a process exit state.

The @debugserver_test and @lldb_test for $k now properly expects
an X notification (signal-caused exit) after killing a just-attached
inferior that was still in the stopped state.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@209108 91177308-0d34-0410-b5e6-96231b3b80d8
Added gdb remote test for one valid qRegisterInfo result.

Checks that at at least qRegisterInfo0 responds with a valid
register info reply packet.  The packet is parsed and validates
that all keys come from the documented set of valid keys.  It
then validates that a minimum set of expected keys
are present in the returned packet.

This test is set to pass on debugserver and fail on llgs TOT.


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@209109 91177308-0d34-0410-b5e6-96231b3b80d8
Build lldb-mi with autotools on Linux. 
THe lldb-mi stuff was not being built on Linux with autotools.
I only added Linux now as I have tested that it build fine on Linux.


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