summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/plugins
diff options
context:
space:
mode:
authorFrederic Riss <friss@apple.com>2018-04-27 00:09:04 +0000
committerFrederic Riss <friss@apple.com>2018-04-27 00:09:04 +0000
commit34ec0bfb5ecee851d31d77a21dd69d49d58eb6b5 (patch)
treebb2ebbd0e9dcc0db454e18d9d7c0eddd103c0f2c /lldb/packages/Python/lldbsuite/test/plugins
parent887fbc61d4ad17842214329dddcd8085d822081a (diff)
downloadbcm5719-llvm-34ec0bfb5ecee851d31d77a21dd69d49d58eb6b5.tar.gz
bcm5719-llvm-34ec0bfb5ecee851d31d77a21dd69d49d58eb6b5.zip
[debugserver] Fix handling of the 'g' packet
LLDB doesn't use this packet so we never hit this, but it looks like some other projects talk to debugserver and are hitting an assert (https://github.com/derekparker/delve/issues/1015). We had an off by 1 in the accounting of the FPU structure sizes. I added a test that basically just check that 'g' doesn't return an error (currently it assert in debug builds). I didn't make it an lldb-server test because it looks like lldb-server doesn't implement the g packet. llvm-svn: 331004
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/plugins')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud