public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/101773] errors when writing to .gcda file are not checked Date: Wed, 04 Aug 2021 14:35:54 +0000 [thread overview] Message-ID: <bug-101773-4-DrEVTMcu6C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101773-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101773 --- Comment #6 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> --- Created attachment 51259 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51259&action=edit added missing error check on fclose in gcc/gcov-io.c Well, not all errors are detected. There is a missing test in gcc/gcov-io.c for fclose (which does a write system call to flush the buffers): --- a/gcc/gcov-io.c +++ b/gcc/gcov-io.c @@ -199,7 +199,8 @@ gcov_close (void) { if (gcov_var.file) { - fclose (gcov_var.file); + if (fclose (gcov_var.file)) + gcov_var.error = 1; gcov_var.file = 0; } gcov_var.mode = 0; (also in attachment). I've tested this patch, and it solves my problem: openat(AT_FDCWD, "dir/#home#vlefevre#a-tst.gcda", O_RDWR|O_CREAT, 0666) = 3 fcntl(3, F_SETLKW, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 fcntl(3, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE) fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 read(3, "", 1024) = 0 lseek(3, 0, SEEK_SET) = 0 write(3, "adcg 02B\233\10\222\21\0\0\0\241\10\0\0\0\1\0\0\0\1\0\0\0\0\0\0\1"..., 84) = -1 ENOSPC (No space left on device) close(3) = 0 write(2, "libgcov profiling error:dir/#hom"..., 68libgcov profiling error:dir/#home#vlefevre#a-tst.gcda:Error writing ) = 68 write(2, "profiling:exiting after an error"..., 33profiling:exiting after an error ) = 33 exit_group(1) = ? +++ exited with 1 +++
next prev parent reply other threads:[~2021-08-04 14:35 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-04 10:20 [Bug gcov-profile/101773] New: " vincent-gcc at vinc17 dot net 2021-08-04 10:35 ` [Bug gcov-profile/101773] " rguenth at gcc dot gnu.org 2021-08-04 11:39 ` vincent-gcc at vinc17 dot net 2021-08-04 12:39 ` marxin at gcc dot gnu.org 2021-08-04 12:50 ` vincent-gcc at vinc17 dot net 2021-08-04 14:09 ` marxin at gcc dot gnu.org 2021-08-04 14:35 ` vincent-gcc at vinc17 dot net [this message] 2021-08-04 15:12 ` marxin at gcc dot gnu.org 2021-08-04 15:15 ` vincent-gcc at vinc17 dot net 2021-08-04 15:27 ` cvs-commit at gcc dot gnu.org 2021-08-04 15:28 ` marxin at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-101773-4-DrEVTMcu6C@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).