Hi Jessica,
You could try executing the following code on the trace resource in the
Traces folder after it has been imported:
try {
resource.setPersistentProperty(TmfCommonConstants.TRACETYPE, /* your
trace type id from org.eclipse.linuxtools.tmf.ui.tracetype extension */ );
resource.setPersistentProperty(TmfCommonConstants.TRACEICON, /* your
plug-in relative icon path */ );
resource.setPersistentProperty(TmfCommonConstants.TRACEBUNDLE, /* your
plug-in bundle id (for the icon) */ );
resource.touch(null);
} catch (CoreException e) {
// TODO Auto-generated catch block
}
Patrick
On Thu, Jul 19, 2012 at 5:50 PM, Zhang, Jessica <jessica.zh...@intel.com>wrote:
> Thanks for debugging the issue Francois, but unfortunately none of the
> work around meets my need.****
>
> ** **
>
> BTW, what I’m really looking for is programmatically associate an imported
> tracing data with a type (kernel/ust) so it can be displayed in the
> viewer. I’m already able to achieve transport remote tracing data to local
> host and create a link to the tracing data folder with the appropriate
> tracing project. But when I try to view the data, I got an error due to
> the tracing data type is not assigned. Any suggestion?****
>
> ** **
>
> Thanks,****
>
> Jessica****
>
> ** **
>
> *From:* linuxtools-dev-boun...@eclipse.org [mailto:
> linuxtools-dev-boun...@eclipse.org] *On Behalf Of *Francois Chouinard
> *Sent:* Thursday, July 19, 2012 12:41 PM
>
> *To:* Linux Tools developer discussions
> *Subject:* Re: [linuxtools-dev] Lttng2 issue****
>
> ** **
>
> Oops. The test on Windows was invalid: after properly installing TCF TE,
> it also failed. So switching to Windows won't solve the issue :-)****
>
> On Thu, Jul 19, 2012 at 3:02 PM, Francois Chouinard <fchouin...@gmail.com>
> wrote:****
>
> Hi Jessica,****
>
> ** **
>
> I finally got back to this issue :-)****
>
> ** **
>
> It seems that the problem occurs when the TCF Target Explorer is installed
> on Eclipse 4.2 on Linux. Also this is not limited to LTTng as you can
> observe the same behavior with a plain CDT project (for instance the
> context menu of the "Includes" pseudo-folder).****
>
> ** **
>
> I opened Bug385543 on TCF so they can have a look.****
>
> ** **
>
> Meanwhile, there are a few workarounds:****
>
> - Remove TCF TE from your Eclipse plugins****
>
> - Revert to Eclipse 3.8****
>
> - Switch to Windows****
>
> ** **
>
> I realize that none of this is great (and one is particularly bad :-))
> but, at this point, we can't do much more.****
>
> ** **
>
> Best Regards,****
>
> /fc****
>
> ** **
>
> On Wed, Jul 18, 2012 at 11:19 PM, Zhang, Jessica <jessica.zh...@intel.com>
> wrote:****
>
> Thanks for the update Francois! - Jessica****
>
> ****
>
> *From:* linuxtools-dev-boun...@eclipse.org [mailto:
> linuxtools-dev-boun...@eclipse.org] *On Behalf Of *Francois Chouinard
> *Sent:* Wednesday, July 18, 2012 8:10 PM****
>
>
> *To:* Linux Tools developer discussions
> *Subject:* Re: [linuxtools-dev] Lttng2 issue****
>
> ****
>
> Hi Jessica,****
>
> ****
>
> I could reproduce under the following conditions:****
>
> - Ubuntu 12.04 (gnome3...)****
>
> - E4.2****
>
> ****
>
> With this combination I get a number of errors (just open the Error Log
> View) with the following stack trace:****
>
> ****
>
> org.eclipse.core.runtime.AssertionFailedException: assertion failed: ****
>
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)****
>
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)****
>
> * at
> org.eclipse.tcf.te.launch.ui.internal.handler.LaunchLaunchConfigurationContributionItem.getContributionItems(LaunchLaunchConfigurationContributionItem.java:87)
> *****
>
> at
> org.eclipse.ui.actions.CompoundContributionItem.getContributionItemsToFill(CompoundContributionItem.java:93)
> ****
>
> at
> org.eclipse.ui.actions.CompoundContributionItem.fill(CompoundContributionItem.java:60)
> ****
>
> at
> org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:125)
> ****
>
> at
> org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:741)****
>
> at
> org.eclipse.jface.action.MenuManager.update(MenuManager.java:822)****
>
> at
> org.eclipse.jface.action.MenuManager.update(MenuManager.java:682)****
>
> at
> org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.showMenu(MenuManagerRendererFilter.java:277)
> ****
>
> at
> org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.handleShow(MenuManagerRendererFilter.java:225)
> ****
>
> at
> org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.safeHandleEvent(MenuManagerRendererFilter.java:207)
> ****
>
> at
> org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.access$1(MenuManagerRendererFilter.java:143)
> ****
>
> at
> org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter$SafeWrapper.run(MenuManagerRendererFilter.java:130)
> ****
>
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)**
> **
>
> at
> org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.handleEvent(MenuManagerRendererFilter.java:140)
> ****
>
> at
> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)****
>
> at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1483)
> ****
>
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1275)***
> *
>
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1300)***
> *
>
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1281)***
> *
>
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198)****
>
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:3596)*
> ***
>
> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3169)****
>
> at
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1022)
> ****
>
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> ****
>
> at
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:916)
> ****
>
> at
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> ****
>
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:585)**
> **
>
> at
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> ****
>
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:540)
> ****
>
> at
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)****
>
> at
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> ****
>
> at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> ****
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> ****
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> ****
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
> ****
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> ****
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)**
> **
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> ****
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ****
>
> at java.lang.reflect.Method.invoke(Method.java:601)****
>
> at
> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)****
>
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)****
>
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)****
>
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)****
>
> ****
>
> ****
>
> ****
>
> When I remove TCF from my Eclipse configuration, everything works fine on
> all the combinations I tried (except we lose the tracer control for the
> legacy LTTng - a pretty deprecated feature anyway).****
>
> ****
>
> I will work further on it tomorrow when I come in.****
>
> ****
>
> Good eventing,****
>
> /fc****
>
> ****
>
> ****
>
> On Wed, Jul 18, 2012 at 9:09 PM, Francois Chouinard <fchouin...@gmail.com>
> wrote:****
>
> OK, I could reproduce. Looking into the issue.****
>
> ****
>
> On Wed, Jul 18, 2012 at 6:08 PM, Zhang, Jessica <jessica.zh...@intel.com>
> wrote:****
>
> The spy report didn't give me any info. I can’t drag and drop since that
> won’t fix the issue that I’m investigating. BTW, I’ve created another
> screen shot that show how does new look like.****
>
> ****
>
> ****
>
> ****
>
> *From:* linuxtools-dev-boun...@eclipse.org [mailto:
> linuxtools-dev-boun...@eclipse.org] *On Behalf Of *Patrick Tasse
> *Sent:* Wednesday, July 18, 2012 2:11 PM****
>
>
> *To:* Linux Tools developer discussions
> *Subject:* Re: [linuxtools-dev] Lttng2 issue****
>
> ****
>
> Hi Jessica,
>
> We're puzzled by the "New". I don't know if it would be helpful, but what
> does the Plug-in Menu Spy report? (Alt-Shift-F2)
>
> In the meantime you could try drag & dropping your traces from an external
> file manager onto the Traces folder, unless that fails also?
>
> Patrick****
>
> On Wed, Jul 18, 2012 at 4:02 PM, Zhang, Jessica <jessica.zh...@intel.com>
> wrote:****
>
> I believe I’m using the Project Explorer and on Tracing perspective. I’m
> attaching the screenshot****
>
> ****
>
> ****
>
> ****
>
> *From:* linuxtools-dev-boun...@eclipse.org [mailto:
> linuxtools-dev-boun...@eclipse.org] *On Behalf Of *Patrick Tasse
> *Sent:* Wednesday, July 18, 2012 12:54 PM
> *To:* Linux Tools developer discussions
> *Subject:* Re: [linuxtools-dev] Lttng2 issue****
>
> ****
>
> Hi Jessica,
>
> The TMF navigator content binding is only applied to the Project Explorer.
> Are you using that view and not Package Explorer or Navigator?
>
> Patrick****
>
> On Wed, Jul 18, 2012 at 3:33 PM, Zhang, Jessica <jessica.zh...@intel.com>
> wrote:****
>
> Hi,
>
> I'm playing with lttng2 on Juno, what I've installed is Lttng-Linux
> Tracing Toolkit, 1.0.0.201206130106. After creating a tracing project, I
> try to import tracing data, but when I right click on the Traces folder, I
> only see "New" no "Import" etc, also the "New" has not effect at all. So
> what am I missing here?
>
> Thanks,
> Jessica
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev****
>
> ****
>
>
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev****
>
> ****
>
>
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev****
>
>
>
> ****
>
> ****
>
> --
> Francois****
>
>
>
> ****
>
> ****
>
> --
> Francois****
>
>
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev****
>
>
>
> ****
>
> ** **
>
> --
> Francois****
>
>
>
> ****
>
> ** **
>
> --
> Francois****
>
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
>
>
_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
