diff options
| author | Pavel Labath <labath@google.com> | 2017-12-22 10:26:59 +0000 |
|---|---|---|
| committer | Pavel Labath <labath@google.com> | 2017-12-22 10:26:59 +0000 |
| commit | b8318155eb071ae2ad6ba94fd7865395e36c35b4 (patch) | |
| tree | 85d744ee2f4e4e057cc4c2cfef3f79b3cc07c0f9 /lldb/packages/Python/lldbsuite/__init__.py | |
| parent | 57493e29198836bfcdab58c0780c106a4f7f30c8 (diff) | |
| download | bcm5719-llvm-b8318155eb071ae2ad6ba94fd7865395e36c35b4.tar.gz bcm5719-llvm-b8318155eb071ae2ad6ba94fd7865395e36c35b4.zip | |
Enable TestReadMemCString on non-darwin targets
The test works fine on linux, and I believe other targets should not
have an issue with as well. If they do, we can start blacklisting
instead of whitelisting.
The idea of using "-1" as the value of the pointer on non-apple targets
backfired, as it fails the "address != LLDB_INVALID_ADDRESS" test (-1 is
the value of LLDB_INVALID_ADDRESS). However, it should be safe to use
0x100 for other targets as well. The first page of memory is generally
kept unreadable to catch null pointer dereferences.
llvm-svn: 321353
Diffstat (limited to 'lldb/packages/Python/lldbsuite/__init__.py')
0 files changed, 0 insertions, 0 deletions
