summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/objc/objc-class-method/TestObjCClassMethod.py
diff options
context:
space:
mode:
authorRui Ueyama <ruiu@google.com>2017-09-27 21:38:02 +0000
committerRui Ueyama <ruiu@google.com>2017-09-27 21:38:02 +0000
commit283f56ac03cfa4168cdd45045539e28e8d9fc92e (patch)
treed290996d08d0d7812153fa3a0c0569a19ef5dac9 /lldb/packages/Python/lldbsuite/test/lang/objc/objc-class-method/TestObjCClassMethod.py
parent88f2aa12d9c8677934329799026d866e2a1cfd1b (diff)
downloadbcm5719-llvm-283f56ac03cfa4168cdd45045539e28e8d9fc92e.tar.gz
bcm5719-llvm-283f56ac03cfa4168cdd45045539e28e8d9fc92e.zip
Fix off-by-one error in TarWriter.
The tar format originally supported up to 99 byte filename. The two extensions are proposed later: Ustar or PAX. In the UStar extension, a pathanme is split at a '/' and its "prefix" and "suffix" are stored in different locations in the tar header. Since "prefix" can be up to 155 byte, it can represent up to 254 byte filename (but exact limit depends on the location of '/' character in a pathname.) Our TarWriter first attempt to use UStar extension and then fallback to PAX extension. But there's a bug in UStar header creation. "Suffix" part must be a NUL- terminated string, but we didn't handle it correctly. As a result, if your filename just 100 characters long, the last character was droppped. This patch fixes the issue. Differential Revision: https://reviews.llvm.org/D38149 llvm-svn: 314349
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/objc/objc-class-method/TestObjCClassMethod.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud