I forgot to send the stack trace from workspace/.metadata/.log . I think
it might be helpful
java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:218)
at
org.eclipse.linuxtools.oprofile.core.linux.LinuxOpcontrolProvider.setupDaemon(LinuxOpcontrolProvider.java:179)
at
org.eclipse.linuxtools.oprofile.launch.launching.AbstractOprofileLaunchConfigurationDelegate.oprofileSetupDaemon(AbstractOprofileLaunchConfigurationDelegate.java:130)
at
org.eclipse.linuxtools.oprofile.launch.launching.OprofileLaunchConfigurationDelegate.preExec(OprofileLaunchConfigurationDelegate.java:42)
at
org.eclipse.linuxtools.oprofile.launch.launching.AbstractOprofileLaunchConfigurationDelegate.launch(AbstractOprofileLaunchConfigurationDelegate.java:66)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
at
org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:924)
at org.eclipse.debug.internal.ui.DebugUIPlugin
$8.run(DebugUIPlugin.java:1128)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.NullPointerException
at
org.eclipse.linuxtools.oprofile.core.opxml.info.InfoAdapter.createHeaders(InfoAdapter.java:131)
at
org.eclipse.linuxtools.oprofile.core.opxml.info.InfoAdapter.process(InfoAdapter.java:124)
at
org.eclipse.linuxtools.oprofile.core.linux.OpxmlRunner.run(OpxmlRunner.java:106)
at org.eclipse.linuxtools.oprofile.core.linux.LinuxOpxmlProvider
$OpInfoRunner.run(LinuxOpxmlProvider.java:55)
at org.eclipse.linuxtools.oprofile.core.linux.LinuxOpxmlProvider
$OpInfoRunner.run0(LinuxOpxmlProvider.java:46)
at
org.eclipse.linuxtools.oprofile.core.daemon.OpInfo.getInfo(OpInfo.java:85)
at
org.eclipse.linuxtools.oprofile.core.Oprofile._initializeOprofileCore(Oprofile.java:94)
at
org.eclipse.linuxtools.oprofile.core.Oprofile.initializeOprofileModule(Oprofile.java:64)
at
org.eclipse.linuxtools.oprofile.core.Oprofile.<clinit>(Oprofile.java:43)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:196)
... 9 more
- daniel
On Fri, 2011-02-11 at 14:08 -0200, danie...@br.ibm.com wrote:
> On Fri, 2011-02-11 at 09:35 -0500, Severin Gehwolf wrote:
> > On Fri, 2011-02-11 at 10:04 -0200, Daniel HB wrote:
> > > On Thu, 2011-02-10 at 15:21 -0500, Severin Gehwolf wrote:
> > > > On Thu, 2011-02-10 at 13:24 -0600, Maynard Johnson wrote:
> > > > > Severin Gehwolf wrote:
> > > > > > On Thu, 2011-02-10 at 08:48 -0600, Maynard Johnson wrote:
> > > > > >> Severin Gehwolf wrote:
> > > > > >>> On Thu, 2011-02-10 at 09:28 -0500, Andrew Overholt wrote:
> > > > > >>>> * William Cohen <wco...@redhat.com> [2011-02-10 09:27]:
> > > > > >>>>> On 02/10/2011 09:19 AM, Andrew Overholt wrote:
> > > > > >>>>>>> what's the status of abandoning opxml?
> > > > > >>>>>>> It seems to me that it's still in use...
> > > > > >>>>>>
> > > > > >>>>>> The upcoming 0.7 release removes its use.
> > > > > >>>>>>
> > > > > >>>>>> Andrew
> > > > > >>>>>> _______________________________________________
> > > > > >>>>>> linuxtools-dev mailing list
> > > > > >>>>>> linuxtools-dev@eclipse.org
> > > > > >>>>>> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> > > > > >>>>>
> > > > > >>>>>
> > > > > >>>>> Cool, that would allow the elimination of oprofile-devel and
> > > > > >>>>> it's undesirable static libraries.
> > > > > >>>>>
> > > > > >>>>> Is 0.7 going to make it for Fedora 15?
> > > > > >>>>
> > > > > >>>> Perhaps. I'll also have to verify my above statement :)
> > > > > >>>
> > > > > >>> The R0_7_0 tag and trunk don't use opxml anymore. What's left is
> > > > > >>> some
> > > > > >>> left-over code removal and documentation update.
> > > > > >
> > > > > >> So I presume the updated oprofile plugin will leverage the native
> > > > > >> XML
> > > > > >> output from opreport, right?
> > > > > >
> > > > > > Yes.
> > > > > >
> > > > > >> And how about the events list? Does it
> > > > > >> use the XML output from ophelp?
> > > > > >
> > > > > > Yes.
> > > > > >
> > > > > >> If so, this is really good news from
> > > > > >> my perspective since (as I had noted in my Jan 14 posting) the
> > > > > >> current
> > > > > >> version of this plugin is completely broken for IBM Power systems.
> > > > > >
> > > > > > We would very much appreciate feedback about the Eclipse oprofile
> > > > > > plug-in >= 0.7.0 on IBM Power systems.
> > > >
> > > > > My team member, Daniel (on cc), will have a look. I presume he should
> > > > > install from
> > > > > http://download.eclipse.org/technology/linuxtools/updates-nightly?
> > > >
> > > > Yes. He can use
> > > > http://wiki.eclipse.org/images/7/77/Eclipse-oprofile_testproj_factorial.zip
> > > > as an example project to try profiling from within Eclipse.
> > >
> > > Just made the test using the factorial project. Got the following error
> > > on a popup window called "Problem occurred":
> > >
> > > "Launching factorial" has encountered a problem.
> > >
> > > An internal error occurred during: "Launching factorial".
> > >
> > >
> > > When hitting the "Details" button:
> > >
> > > An internal error occurred during: "Launching factorial".
> > > java.lang.ExceptionInInitializerError
> > >
> > >
> > > Test was done using Eclipse SDK 3.6.2 with CDT 7.0.2. Java version
> > > 1.5.0. OS used was RHEL 6.0. processor was a Power6 3,5Ghz on a LPar
> > > with 2GB of RAM.
> >
> > I assume you did: Right click on binary in CDT view => Profile as =>
> > Profile with Oprofile, right?
>
> Precisely.
>
> >
> > Can you run the binary without errors? Right click => Run as => Local
> > C/C++ Application
> >
> > Just making sure this isn't a CDT problem :)
>
> Hehehe sorry, forgot to mention that. Project runs fine as local
> application, but fails to profile with Oprofile.
>
> >
> > Thanks,
> > --Severin
> >
> >
_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
