Support nwere versions of the Segger J-Link jtag board software.
authorJason Molenda <jmolenda@apple.com>
Tue, 23 Oct 2018 23:45:56 +0000 (23:45 +0000)
committerJason Molenda <jmolenda@apple.com>
Tue, 23 Oct 2018 23:45:56 +0000 (23:45 +0000)
commitdf9f796fbb91fd9c16fab8eb6535f0f5b937e452
tree444dee36bfb35451aaa0844298afd178914e5813
parent5fa1e35bcc99dbdeee4e966e21670f9d537c79f7
Support nwere versions of the Segger J-Link jtag board software.
Add support in ProcessGDBRemote::GetGDBServerRegisterInfo
for recognizing a generic "arm" architecture that will be used if
nothing better is available so that we don't ignore the register
definitions if we didn't already have an architecture set.
Also in ProcessGDBRemote::DoConnectRemote don't set the target
arch unless we have a valid architecture to set it to.

Platform::ConnectProcess will try to get the current target's
architecture, or the default architecture, when creating the
target for the connection to be attempted.  If lldb was started
with a target binary, we want to create this target with that
architecture in case the remote gdb stub doesn't supply a
qHostInfo arch.

Add logging to Target::MergeArchitecture.

<rdar://problem/34916465>

llvm-svn: 345106
lldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/TestArmRegisterDefinition.py [new file with mode: 0644]
lldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/gdbclientutils.py
lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
lldb/source/Target/Platform.cpp
lldb/source/Target/Target.cpp