Bug 128739 - Oprofile generates exception
Summary: Oprofile generates exception
Status: MODIFIED
Alias: None
Product: Red Hat Developer Suite
Classification: Retired
Component: Profiling Plug-in   
(Show other bugs)
Version: 2.0
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Keith Seitz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-28 20:59 UTC by Aaron Luchko
Modified: 2008-05-01 15:39 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
logfile (57.54 KB, text/plain)
2004-07-28 21:01 UTC, Aaron Luchko
no flags Details

Description Aaron Luchko 2004-07-28 20:59:28 UTC
Description of problem:
When running on a machine without smp you can generate an exception
trying to make an oprofile project.

Version-Release number of selected component (if applicable):
eclipse-oprofile-1.1.0-5

How reproducible:
always

Steps to Reproduce:
1. Make a C project
2. Run -> Run, Profile C/C++ Application, select new
3. When it prompts you for a password hit cancel
  
Actual results:
It cancels displays a message noting that the Oprofile kernel module
couldn't be loaded and generates an exception in the log file, if you
try to click the "New" button again nothing happens but this message
is generated on the command line
"
 Unhandled event loop exception
Reason:
java.lang.NullPointerException
Unhandled event loop exception
"


Expected results:
It should cancel gracefully and not give any message about the
oprofile module since you cancelled so it shouldn't try and load it.

Comment 1 Aaron Luchko 2004-07-28 21:01:36 UTC
Created attachment 102271 [details]
logfile

logfile from canceling the password dialogue, getting the error message, then
clicking "New" once.


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