Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 327840

Summary:	Plug-in "org.eclipse.linuxtools.oprofile.core" was unable to instantiate class "org.eclipse.linuxtools.oprofile.core.linux.x86_64.LinuxOpxmlProvider64".
Product:	z_Archived	Reporter:	jacoblanchaster
Component:	LinuxTools	Assignee:	OProfile Inbox <linux.oprofile-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	kksebasti, remy.suen, sgehwolf
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description jacoblanchaster

2010-10-14 19:46:54 EDT

Build Identifier: I20100608-0911

When I try to run Oprofile, I receive the error message:

Plug-in "org.eclipse.linuxtools.oprofile.core" was unable to instantiate class "org.eclipse.linuxtools.oprofile.core.linux.x86_64.LinuxOpxmlProvider64".

According to the README located in org.eclipse.linuxtools.oprofile.core(0.3.0.201008261754), I tried to run ./install in the natives/linux/scripts directory. This script told me to run ./install-noconsolehelper.sh, which I did. This script gave an error message due to opxml not being built. I built opxml in natives/linux/opxml and then ran ./install-noconsolehelper.sh again. This time, the script indicated that installation was successful.

Reproducible: Always

Steps to Reproduce:
1.Use Gentoo
2.Install Eclipse 3.6 and use Eclipse Marketplace to install linuxtools.
3.Make opxml. The Gentoo package oprofile does not have all the libraries and headers installed, but the package downloaded by Gentoo does. In addition, the library names need to be renamed to work with the opxml make script.
4.Follow the instructions in the details section.
5.Open eclipse, left click on something to be profiled and select Profile As. The simple act of selecting Oprofile with give an error message.

Comment 1 jacoblanchaster

2010-10-14 19:54:39 EDT

When i run ./eclipse -console and run ss, I notice that

org.eclipse.linuxtools.oprofile.core(0.3.0.201008261754)

does not have a fragment listed despite the declaration in its MANIFEST.MF file. The fragment

org.eclipse.linuxtools.oprofile.core.linux.x86_64(0.3.0.201008261754) does not have a master listed despite the declaration in its MANIFEST.MF file.

The fragment org.eclipse.linuxtools.oprofile.core.linux.x86_64 contains the class LinuxOpxmlProvider64.class.

Comment 2 Severin Gehwolf

2010-10-19 09:52:36 EDT

(In reply to comment #1)
> When i run ./eclipse -console and run ss, I notice that
> 
> org.eclipse.linuxtools.oprofile.core(0.3.0.201008261754)
> 
> does not have a fragment listed despite the declaration in its MANIFEST.MF
> file. The fragment
> 
> org.eclipse.linuxtools.oprofile.core.linux.x86_64(0.3.0.201008261754) does not
> have a master listed despite the declaration in its MANIFEST.MF file.
> 
> The fragment org.eclipse.linuxtools.oprofile.core.linux.x86_64 contains the
> class LinuxOpxmlProvider64.class.

I wonder if this is a x86_64 problem. Do you have access to a 32 bit box (or VM) using Gentoo? Is something similar happening on a 32 bit x86 box?

Thanks!

Comment 3 Roland Grunberg

2011-09-29 15:01:34 EDT

The org.eclipse.linuxtools.oprofile.core.linux.${arch} packages were removed as a result of switching away from opxml. It seems like this may have been an issue with those packages being referenced in the manifest despite having been removed. As of now, there are no references to those old packages.

Resolving as fixed.