forked from OSchip/llvm-project
5b2e968264
On Windows at least, llvm-strings was crashing if it encountered bytes that mapped to negative chars, as it was passing these into std::isgraph and std::isblank functions, resulting in undefined behaviour. On debug builds using MSVC, these functions verfiy that the value passed in is representable as an unsigned char. Since the char is promoted to an int, a value greater than 127 would turn into a negative integer value, and fail the check. Using the llvm::isPrint function is sufficient to solve the issue. Reviewed by: ruiu, mstorsjo Differential Revision: https://reviews.llvm.org/D53509 llvm-svn: 345137 |
||
|---|---|---|
| .. | ||
| Inputs | ||
| all-sections.test | ||
| archive-filename.test | ||
| file-filename.test | ||
| length.test | ||
| negative-char.test | ||
| nested-archives.test | ||
| radix.test | ||
| stdin-filename.test | ||
| terminator-neg.test | ||
| terminator.test | ||