[news.eclipse.technology.linuxtools] Re: OProfile on openSUSE 11.1

[Kent Sebastian <ksebasti@xxxxxxxxxx>]

Oh boy, I expected some problems with 0.1 but not this many ;)

Axel Mueller wrote:
> OK, I recompiled opxml and put it in the aforementioned directory. 
> Calling opxml from the command line now works. However, I still have 
> problems with the Eclipse plugin.
> - no events are shown in the launch configuration

What is the output of `opxml info`? In the 'defaults' section, does the 
'log-file' path correct? Does the oprofile command `ophelp` show events?

> - the oprofile view is now filled with some data but I can only see the 
> top of the tree (100% in myapp); I cannot dive in deeper (opreport shows 
> much more)

If the samples were not created from a launch within Eclipse then the 
view will not show the data properly, this was fixed to show an error in 
SVN a while back. The reason is the plugin is expecting a single binary 
to be in the samples; as in, opcontrol is setup with an --image=<binary> 
filter (the plugin isn't meant to be a direct front-end to oprofile, 
rather to make oprofile useful to c/c++ Eclipse devs).

If the binary was profiled from within Eclipse and it doesn't show any 
symbols/samples, but opreport does, file a bug at eclipse.org and attach 
sample files please :)

> - there are still errors in the Eclipse error log

Which? :) If it's a readerSpawner error (or something similar) that's
a cdt issue which has eluded many people AFAIK.