summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/event/TestEvents.py
diff options
context:
space:
mode:
authorKevin Enderby <enderby@apple.com>2016-05-05 17:43:35 +0000
committerKevin Enderby <enderby@apple.com>2016-05-05 17:43:35 +0000
commitb34e3a1877fb095b0386c7e3675aca66ff26edeb (patch)
tree8b7feb2abd31e5cae269ee6525fa3613d142a804 /lldb/packages/Python/lldbsuite/test/python_api/event/TestEvents.py
parent226a734f1a21db545d24135d6714bda31a08d78b (diff)
downloadbcm5719-llvm-b34e3a1877fb095b0386c7e3675aca66ff26edeb.tar.gz
bcm5719-llvm-b34e3a1877fb095b0386c7e3675aca66ff26edeb.zip
Clean up the specific error message for a malformed Mach-O files with bad segment
load commands. The existing test case in test/Object/macho-invalid.test for macho-invalid-too-small-segment-load-command has a cmdsize of 55, while being too small also it is not a multiple of 4. So when that check is added this test case will produce a different error. So I constructed a new test case that will trigger the intended error. I also changed the error message to be consistent with the other malformed Mach-O file error messages which prints the load command index. I also removed both object_error::macho_load_segment_too_small and object_error::macho_load_segment_too_many_sections from Object/Error.h as they are not needed and can just use object_error::parse_failed and let the error message string distinguish the specific error. llvm-svn: 268652
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/event/TestEvents.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud