Description of problem: I wouldn't normally mention this except that it's a regression over Fedora 16 where valgrind apparently cleans up properly. For example, after a short test involving valgrind, I've got lots of these files in my non-standard TMPDIR: vgdb-pipe-from-vgdb-to-18823-by-rjones-on-spin.home.annexia.org vgdb-pipe-from-vgdb-to-19983-by-rjones-on-spin.home.annexia.org vgdb-pipe-from-vgdb-to-20067-by-rjones-on-spin.home.annexia.org vgdb-pipe-from-vgdb-to-20535-by-rjones-on-spin.home.annexia.org vgdb-pipe-from-vgdb-to-20922-by-rjones-on-spin.home.annexia.org vgdb-pipe-shared-mem-vgdb-18823-by-rjones-on-spin.home.annexia.org vgdb-pipe-shared-mem-vgdb-19983-by-rjones-on-spin.home.annexia.org vgdb-pipe-shared-mem-vgdb-20067-by-rjones-on-spin.home.annexia.org vgdb-pipe-shared-mem-vgdb-20535-by-rjones-on-spin.home.annexia.org vgdb-pipe-shared-mem-vgdb-20922-by-rjones-on-spin.home.annexia.org vgdb-pipe-to-vgdb-from-18823-by-rjones-on-spin.home.annexia.org vgdb-pipe-to-vgdb-from-19983-by-rjones-on-spin.home.annexia.org vgdb-pipe-to-vgdb-from-20067-by-rjones-on-spin.home.annexia.org vgdb-pipe-to-vgdb-from-20535-by-rjones-on-spin.home.annexia.org vgdb-pipe-to-vgdb-from-20922-by-rjones-on-spin.home.annexia.org Version-Release number of selected component (if applicable): 1:valgrind-3.7.0-1.fc17.x86_64 How reproducible: 100% Steps to Reproduce: 1. Use valgrind on just about any program. 2. 3. Actual results: Temporary file is left around. Expected results: It used to be cleaned up. Additional info:
Hmmm, maybe this doesn't happen on "just any program". I'm going to look at this a bit more ...
(In reply to comment #1) > Hmmm, maybe this doesn't happen on "just any program". > I'm going to look at this a bit more ... Have you looked a bit more? Might this be related/similar to https://bugzilla.redhat.com/show_bug.cgi?id=803725
I don't think this happens any more, so closing.