New compilers break on potentially passing NULL to printf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdbtools (Debian) |
New
|
Unknown
|
|||
mdbtools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
While the build tries to hide the error (>dev/null 2>&1) it can be reproduced and then shows:
In function ‘printf’,
inlined from ‘mdb_dump_catalog’ at catalog.c:198:4:
/usr/include/
112 | return __printf_chk (__USE_
| ^~~~~~~
cc1: all warnings being treated as errors
I've found that to be a real issue with new toolchains identifying a problem in the code.
FYI - I've reported the same upstream
https:/
And found a related Debian issue
https:/
Changed in mdbtools (Debian): | |
status: | Unknown → New |
tags: | added: update-excuse |
Upstream seems generally +1 I've revised my patch there and with that we are unlikely to carry an odd delta for this forever.
Uploading a fixed version to impish based on what is discussed there.