From Bug 1116387
> > - create new profile configuration with oprofile, uncheck "Use default event"
> > checkbox, select CPU_CLK_UNHALTED (I use often virtual machines...).
> > - Apply, Profile, profiling works like a charm
> > Then...
> > - open profiling configurations, select the same one, Profiler tab, Events
> > "Use default event" is unchecked, Counter tab is empty
> > - if I click on Profile button to perform profiling, it starts and runs fine
> > far as I can tell)
> > - if I click on "Use default events", Counter tab gets filled and is grayed
> > to sign me that it's not enabled, which is in fact correct, because "Use
> > event" box is now checked. Unchecking "Use default event" makes Counter tab
> > available and I'm able to select events.
> I've been able to reproduce this particular issue as well. This would appear to
> be https://bugs.eclipse.org/bugs/show_bug.cgi?id=436655 . For the "Profile
> Configurations" dialog, we have a combo box that lists various profiling
> launches (perf, oprofile, massif, etc.) and once selected, will change the tabs
> as required. We call layout() to redraw the newly loaded tabs and this seems to
> be an issue on GTK3. Note that if you go to Profiling Tools -> Profiling Tools
> Configurations (instead of Profile As -> Profile Configurations) and then create
> a "Profile With OProfile" and do the same as before, the Events Tab will be draw
> as expected (we don't call layout() here) . Furthermore adding the 2 lines :
> '--launcher.GTK_version' and '2' right below 'openFile' in
> /opt/rh/devtoolset-3/root/etc/eclipse.ini also fixes the issue. In addition,
> because the problem is with GTK3, this behaviour shouldn't be happening on RHEL
> 6 (has GTK 2).
> I'm aware of some work being done by Alex to try and resolve this but I'm also
> looking into any way of avoiding that layout() call.
No resources for fixing this. Postponing.
Roland, would you please check whether this bug is fixed?
I think this might still be an issue. I haven't tested against Oprofile yet but the same type of problem also exists against the Callgraph options.
Okay, thanks for looking.
According to the upstream bug, this should have been fixed in Eclipse (Neon) 4.6M3. I think the last time we tested this out, it would have been against 4.5 (Mars).
I could try testing this out, and if the report is correct, we can mark this as having been fixed upstream, and as a result, fixed in our new release channel.
Roland, please verify this is fixed and act according to the results on this bug.
I just tried this out but was unable to reproduce. That is, after profiling a simple C application with CPU_CLK_UNHALTED, and going back to the profile configuration for OProfile, under Events, the Counter tab is fully visible and other events may be seen. Does it make sense to mark this as CLOSED (UPSTREAM) ?
Marking as CLOSED (UPSTREAM). This was very likely fixed by https://bugs.eclipse.org/bugs/show_bug.cgi?id=470129 (Eclipse Neon, 4.6M3). https://bugs.eclipse.org/bugs/show_bug.cgi?id=436655 was basically a duplicate of that one.