Re: scripts/basic/fixdep: Complete error handling in print_cmdline()

From: SF Markus Elfring
Date: Sun Oct 30 2016 - 11:19:42 EST

Next message: Peter Meerwald-Stadler: "Re: [PATCH v3 2/8] iio: inkern: add helpers to query available values from channels"
Previous message: Greg KH: "Re: [PATCH] Staging: ks7010: ks7010_sdio.c: Fixed a coding style issue."
In reply to: Jim Davis: "Re: [PATCH 09/10] scripts/basic/fixdep: Complete error handling in print_cmdline()"
Next in thread: SF Markus Elfring: "[PATCH 10/10] scripts/basic/fixdep: Combine two fprintf() calls into one fputs() call in usage()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> But what would you expect printf error checking to tell a user?

I wonder that the error detection and corresponding exception handling
was not corrected for the affected source files of build-time tools so far.
https://www.securecoding.cert.org/confluence/display/c/EXP12-C.+Do+not+ignore+values+returned+by+functions

Regards,
Markus

Next message: Peter Meerwald-Stadler: "Re: [PATCH v3 2/8] iio: inkern: add helpers to query available values from channels"
Previous message: Greg KH: "Re: [PATCH] Staging: ks7010: ks7010_sdio.c: Fixed a coding style issue."
In reply to: Jim Davis: "Re: [PATCH 09/10] scripts/basic/fixdep: Complete error handling in print_cmdline()"
Next in thread: SF Markus Elfring: "[PATCH 10/10] scripts/basic/fixdep: Combine two fprintf() calls into one fputs() call in usage()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]