Hide Forgot
Description of problem: When defining a new Oprofile launch configuration, you can proceed without specifying a corresponding C/C++ launch configuration. Version-Release number of selected component (if applicable): snapshot-20040331 How reproducible: Always Steps to Reproduce: 1. Define a new Profiling launch configuration 2. Don't specify a corresponding C/C++ launch configuration Actual results: You are allowed to continue (and even run oprofile) without specifying a C/C++ launch configuration. Expected results: The user shouldn't be allowed to continue without specifying a C/C++ launch configuration. The dialog should probably do setFinish(false) or whatever it is if the C/C++ launch config entry box is empty or invalid (invalid == the C/C++ launch config entered doesn't actually exist).
Actually this is the intended behavior. A system-wide profiler does not necessarily need anything special to run it. What if I want some sort of system performance baseline to compare what my application does to the system?