usb: dwc3: fix coverity warning CHECKED_RETURN Browse files Added return value conditional checks to fix the below Coverity warning, Also added return value error handling for the same: Warning Type: Unchecked return value (CHECKED_RETURN). Category: Error handling issues. Signed-off-by: ...
860 if (ret < 0) { 861 /*send wake up command twice because of an expected nack return in power down mode*/ >>> CID 434739: Error handling issues (CHECKED_RETURN) >>> Calling "scd4x_write_command" without checking return value (as is done elsewhere 21 out of 23 times). 862 scd...
Coverity8.7.1检查器说明书 CoverityAnalysis、CoverityPlatform和CoverityDesktop说明 版权2017,Synopsys,Inc.。在全球保留所有权利。 ii 目录 1.概述...1 1.1.质量检查器...1 1.2.安全检查器...
# TODO: For some reasons this does not fully load on Debian 10 (Haven't checked if it happens on other distros yet), it breaks source packaging/installer/functions.sh || echo "Failed to fully load the functions library" cpus=$(find_processors) [ -z "${cpus}" ] && cpus=1 if...
return NULL; } @@ -826,7 +838,7 @@ void db_close() { case url_ftp: { if (conf->db_out!=NULL) { - url_fclose(conf->db_out); + url_fclose((URL_FILE*)conf->db_out); } break; } diff -up ./src/db_disk.c.coverity ./src/db_disk.c ...
*** CID 1472579: Error handling issues (CHECKED_RETURN) /cpukit/mghttpd/mongoose.c: 3716 in put_file() 3710 } else { 3711 fclose_on_exec(&file); 3712 range = mg_get_header(conn, "Content-Range"); 3713 r1 = r2 = 0; 3714 if (range != NULL && parse_range_header(range, &r1...
I checked an example code with three compilers and noticed no standardrelated warnings. I can ask on a C/C++ mailing list if the code isstandard compliant. It could be Coverity bug. #include <cstddef> void f(void); static_assert(f != NULL, "f"); ...
参考译文 Coverity <!DOCTYPE html> 登录_法语助手在线词典
>>> CID 434659: Error handling issues (CHECKED_RETURN) >>> Calling "gpio_pca_series_reg_cache_update" without checking return value (as is done elsewhere 4 out of 5 times). 379 gpio_pca_series_reg_cache_update(dev, reg_type, buf); ...
861 */ >>> CID 318635: Error handling issues (CHECKED_RETURN) >>> Calling "ticker_stop" without checking return value (as is done elsewhere 9 out of 11 times). 862 ticker_stop(TICKER_INSTANCE_ID_CTLR, TICKER_USER_ID_ULL_HIGH, 863 TICKER_ID_SCAN_STOP, NULL, NULL); 864 865 /* ...