Fix gdb-remote qMemoryRegionInfo unit tests for xml-enabled builds
authorPavel Labath <labath@google.com>
Wed, 2 May 2018 17:00:33 +0000 (17:00 +0000)
committerPavel Labath <labath@google.com>
Wed, 2 May 2018 17:00:33 +0000 (17:00 +0000)
commit47776cbd2cbd0af79150c4988b44cfcc6cb39d96
tree73a7d14cc818caa8cda0aac85461df3303fae9bf
parentd8f460e864307f6cf71d9dec63fe3a99ddb4f2b5
Fix gdb-remote qMemoryRegionInfo unit tests for xml-enabled builds

In case we are building with xml enabled, the GetMemoryRegionInfo
function will send extra packets to query te extended memory map, which
the tests were not expecting.

Add an expectation for this to the test. Right now, it's just a basic
one which pretends we don't support the extension, however, it would be
also interesting the add a test which verifies the extension-enabled
case.

I also noticed that the test does a pretty lousy job of validating the
returned memory region info, so I add a couple of extra assertions to
improve that.

llvm-svn: 331374
lldb/unittests/Process/gdb-remote/GDBRemoteCommunicationClientTest.cpp