#227 opreport uses oprofile_data even when passed an archive spec


By default (as of 0.9.8), opreport will first look for a samples directory in <cur-dir>/oprofile_data. However, if the user passes an archive specification, it should honor that spec and ignore any <cur-dir>/oprofile_data dirctory it finds, but it is not ignoring it.


  • Maynard Johnson

    Maynard Johnson - 2012-12-21
    • status: open --> closed-invalid
  • Maynard Johnson

    Maynard Johnson - 2012-12-21

    This was a user error on my part. As of oprofilie 0.9.8, when oparchive is run, it prints the following message:

    Example: The pathnames below are, of course, variable:
    Using /home/maynard/test-stuff/tmp/oprofile_data/samples/ for session-dir
    NOTE: The sample data in this archive is located at /home/maynard/test-stuff/tmp/oprofile_data
    instead of the standard location of /var/lib/oprofile. Hence, when using opreport
    and other post-processing tools on this archive, you must pass the following option:

    Evidently, when I opened this bug, I had run 'opreport archive:<archive-spec>' without specifying the --session-dir as directed by the message.

    Closing bug.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks