Bug 687968 - oprofile --setup not valid with --save
Summary: oprofile --setup not valid with --save
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: oprofile
Version: 6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: William Cohen
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-15 21:08 UTC by James M. Leddy
Modified: 2018-11-14 13:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 21:31:13 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description James M. Leddy 2011-03-15 21:08:46 UTC
Description of problem:

We have scripts that start, top and save oprofile sessions with the following commands. These used to work fine under RHEL5 but we're seeing this "Option "--setup" not valid with "--save" " error under RHEL6. Is there a way to work around this?

[root@etc759679a eth0]# opcontrol --start --session-dir=/local/tmp/root.lyIVNu --vmlinux=/usr/lib/debug/lib/modules/2.6.32-71.18.1.el6.x86_64/vmlinux --separate=lib --event=CPU_CLK_UNHALTED:6000::0:1
Profiler running.
[root@etc759679a eth0]# opcontrol --stop
Stopping profiling.
[root@etc759679a eth0]# opcontrol --session-dir=/local/tmp/root.lyIVNu --dump
Option "--setup" not valid with "--dump".
[root@etc759679a eth0]# opcontrol --session-dir=/local/tmp/root.lyIVNu --save=CPU_CLK_UNHALTED
Option "--setup" not valid with "--save".

Comment 4 William Cohen 2011-03-16 20:04:44 UTC
The suggest patch is reverting a fix for the case where someone wants to use

opcontrol --setup --session-dir=blah

http://sourceforge.net/tracker/index.php?func=detail&aid=2646398&group_id=16191&atid=116191


The proposed solution is unlikely the right way to do things.

Comment 5 William Cohen 2011-03-16 21:31:13 UTC
The --session-dir shouldn't need to be used for the --dump and --save options. That information is already be in the /root/.oprofile/daemonrc file and in implicitly used by the "opcontrol --save=..." and "opcontrol --dump".

Just use:

 opcontrol --save=CPU_CLK_UNHALTED

The "--stop" implicitly does a "--dump" so the following "opcontrol --dump" is redundant.


Note You need to log in before you can comment on or make changes to this bug.