diff options
| author | Jason Molenda <jmolenda@apple.com> | 2012-12-19 02:54:03 +0000 |
|---|---|---|
| committer | Jason Molenda <jmolenda@apple.com> | 2012-12-19 02:54:03 +0000 |
| commit | f17b5ac6e1239a5ff8c46c0351ba140b35f7a6ab (patch) | |
| tree | b88ee14026d17dae8cc22635ac01bb24e808eede /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.h | |
| parent | 503053a737bf1c54899bcc2d1b4c514485e30054 (diff) | |
| download | bcm5719-llvm-f17b5ac6e1239a5ff8c46c0351ba140b35f7a6ab.tar.gz bcm5719-llvm-f17b5ac6e1239a5ff8c46c0351ba140b35f7a6ab.zip | |
<rdar://problem/11961650>
Update the debugserver "qProcessInfo" implementation to return the
cpu type, cpu subtype, OS and vendor information just like qHostInfo
does so lldb can create an ArchSpec based on the returned values.
Add a new GetProcessArchitecture to GDBRemoteCommunicationClient akin
to GetHostArchitecture. If the qProcessInfo packet is supported,
GetProcessArchitecture will return the cpu type / subtype of the
process -- e.g. a 32-bit user process running on a 64-bit x86_64 Mac
system.
Have ProcessGDBRemote set the Target's architecture based on the
GetProcessArchitecture when we've completed an attach/launch/connect.
llvm-svn: 170491
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunication.h')
0 files changed, 0 insertions, 0 deletions
