This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug gcov-profile/58602] .gcno files not truncated at gcov_close
- From: "law at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 16 Jan 2014 17:24:25 +0000
- Subject: [Bug gcov-profile/58602] .gcno files not truncated at gcov_close
- Auto-submitted: auto-generated
- References: <bug-58602-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58602
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> ---
It seems like all we've done in the last 10 years is rotate through a set of
bugs in this code.
The whole point of the Richard's original removal of ftruncate was to make
things easier for folks on windows & using simulators (newlib). That patch
introduced a race which led to Jakub's change form Feb 2004 to close the race
condition, but which can leave the file untruncated.
So the question is does this introduce a race similar to what Jakub was trying
to fix back in Feb 2004? What testing has been done to see if there's a race.
Testing similar to Jakub's but scaled up for modern hardware would raise the
confidence level of this patch significantly.
http://marc.info/?l=gcc-patches&m=107747608611324&w=2
[ Oddly enough, the gcc.gnu.org archives seem to be missing for this thread and
much of Feb2004. ]