mirror of
https://github.com/Gericom/teak-llvm.git
synced 2025-06-20 12:05:48 -04:00
![]() qemu has a very small maximum packet size (4096) and it actually only uses half of that buffer for some implementation reason, so when lldb asks for the register target definitions, the x86_64 definition is larger than 4096/2 and we need to fetch it in two parts. This patch and test is fixing a bug in GDBRemoteCommunicationClient::ReadExtFeature when reading a target file in multiple parts. lldb was assuming that it would always get back the maximum packet size response (4096) instead of using the actual size received and asking for the next group of bytes. We now have two tests in gdb_remote_client for unique features of qemu - TestNestedRegDefinitions.py would test the ability of lldb to follow multiple levels of xml includes; I opted to create a separate TestRegDefinitionInParts.py test to test this wrinkle in qemu's gdb remote serial protocol stub implementation. Instead of combining both tests into a single test file. <rdar://problem/49537922> |
||
---|---|---|
.. | ||
a.yaml | ||
basic_eh_frame.yaml | ||
gdbclientutils.py | ||
operating_system_2.py | ||
operating_system.py | ||
TestArmRegisterDefinition.py | ||
TestGDBRemoteClient.py | ||
TestGDBRemoteLoad.py | ||
TestJLink6Armv7RegisterDefinition.py | ||
TestNestedRegDefinitions.py | ||
TestNoGPacketSupported.py | ||
TestNoWatchpointSupportInfo.py | ||
TestPlatformClient.py | ||
TestRecognizeBreakpoint.py | ||
TestRegDefinitionInParts.py | ||
TestRestartBug.py | ||
TestStopPCs.py | ||
TestTargetXMLArch.py | ||
TestThreadSelectionBug.py | ||
TestWriteMemory.py |