octoleo/qpdf
2
1
Fork 0
mirror of https://github.com/qpdf/qpdf.git synced 2024-11-12 07:46:28 +00:00
Code Issues Releases Wiki Activity
16f4f94cd9
qpdf/libtests/qtest/qintc/qintc.out

38 lines
2.1 KiB
Plaintext
Raw Normal View History

New safe type converters in QIntC
2019-06-19 22:53:22 +00:00
QIntC::to_int<int32_t>(i1): -1153374643 -1153374643 PASSED
QIntC::to_uint<uint32_t>(u1): 3141592653 3141592653 PASSED
QIntC::to_int<uint32_t>(u1): integer out of range converting 3141592653 from a 4-byte unsigned type to a 4-byte signed type PASSED
QIntC::to_uint<int32_t>(i1): integer out of range converting -1153374643 from a 4-byte signed type to a 4-byte unsigned type PASSED
QIntC::to_int<uint64_t>(ul1): integer out of range converting 1099511627776 from a 8-byte unsigned type to a 4-byte signed type PASSED
QIntC::to_int<uint64_t>(ul2): 12345 12345 PASSED
QIntC::to_uint<uint64_t>(ul2): 12345 12345 PASSED
QIntC::to_offset<uint32_t>(u1): 3141592653 3141592653 PASSED
QIntC::to_offset<int32_t>(i1): -1153374643 -1153374643 PASSED
Fix sign and conversion warnings (major) This makes all integer type conversions that have potential data loss explicit with calls that do range checks and raise an exception. After this commit, qpdf builds with no warnings when -Wsign-conversion -Wconversion is used with gcc or clang or when -W3 -Wd4800 is used with MSVC. This significantly reduces the likelihood of potential crashes from bogus integer values. There are some parts of the code that take int when they should take size_t or an offset. Such places would make qpdf not support files with more than 2^31 of something that usually wouldn't be so large. In the event that such a file shows up and is valid, at least qpdf would raise an error in the right spot so the issue could be legitimately addressed rather than failing in some weird way because of a silent overflow condition.
2019-06-21 03:35:23 +00:00
QIntC::to_ulonglong<int32_t>(i1): integer out of range converting -1153374643 from a 4-byte signed type to a 8-byte unsigned type PASSED
New safe type converters in QIntC
2019-06-19 22:53:22 +00:00
QIntC::to_char<int32_t>(i2): 81 Q PASSED
QIntC::to_uchar<int32_t>(i2): 81 Q PASSED
Don't assume char is signed in int conversion tests (fixes #361)
2019-09-17 16:13:19 +00:00
QIntC::to_uchar<signed char>(c1): integer out of range converting <20> from a 1-byte signed type to a 1-byte unsigned type PASSED
QIntC::to_uchar<char>(c2): W W PASSED
QIntC::to_char<char>(c2): W W PASSED
Handle negative numbers in QIntC::range_check (fuzz issue 26994)
2020-11-21 18:12:31 +00:00
1 + 2: okay PASSED
-1 + 2: okay PASSED
-100 + -200: okay PASSED
max_ll + 0LL: okay PASSED
max_ll + 1LL: adding 1 to 9223372036854775807 would cause an integer overflow PASSED
max_ll + 0LL: okay PASSED
max_ll + 1LL: adding 1 to 9223372036854775807 would cause an integer overflow PASSED
max_ull + 0ULL: okay PASSED
max_ull + 1ULL: adding 1 to 18446744073709551615 would cause an integer overflow PASSED
min_ll + 0LL: okay PASSED
min_ll + -1LL: adding -1 to -9223372036854775808 would cause an integer underflow PASSED
max_sc + max_sc: adding  to  would cause an integer overflow PASSED
'!' + '#': okay PASSED
Add QIntC::range_check_subtract
2021-11-04 17:52:41 +00:00
1 - 2: okay PASSED
-1 - -2: okay PASSED
1 - 10: okay PASSED
-1 - -10: okay PASSED
0LL - min_ll: subtracting -9223372036854775808 from 0 would cause an integer overflow PASSED
1LL - min_ll: subtracting -9223372036854775808 from 1 would cause an integer overflow PASSED
0LL - max_ll: okay PASSED
-1LL - max_ll: okay PASSED
-2LL - max_ll: subtracting 9223372036854775807 from -2 would cause an integer underflow PASSED
Copy Permalink