Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: John Levon <movement@us...> - 2001-09-18 01:00:40
Update of /cvsroot/oprofile/oprofile/doc
In directory usw-pr-cvs1:/tmp/cvs-serv28569/doc
couple of bug fixes, fix mtime and changed binary issue (I doubt the over
head is noticable)
RCS file: /cvsroot/oprofile/oprofile/doc/oprofile.sgml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- oprofile.sgml 2001/09/08 21:46:04 1.25
+++ oprofile.sgml 2001/09/18 01:00:33 1.26
@@ -661,8 +661,9 @@
along with the binary file being profiled, to produce human-readable data. Note that if the binary file changes
after the sample file was created, you won't be able to get useful data out. This situation is detected for you.
A similar scenario can happen when re-starting profiling, as the old sample files from previous sessions don't
-get deleted (allowing you to build profiles over many distinct profiling sessions). However in this case, if the
-binary has changed, the old sample file is automatically deleted for you.
+get deleted (allowing you to build profiles over many distinct profiling sessions).
+If the sample file is determined to be out of date, it is backed up with a different session number (appended to
+the name of the sample file), or deleted, as appropriate.
Note that kernel modules without symbol data (this can happen with some initrd setups) cannot be profiled (modules