Thanks Roland. There are a few errors that seem to be unrelated?
I see 5 or 6 of the following preceding the Valgrind related error: "NLS unused message: ProfileLaunchShortcut.Launcher in: org.eclipse.linuxtools.internal.profiling.launch.messages An exception stack trace is not available." Building works fine... though I do see the following errors occasionally (I think also unrelated to launching Valgrind) java.io.FileNotFoundException: /IMG_OBJ_ADD at org.eclipse.osgi.framework.internal.protocol.bundleentry.Handler.findBundleEntry(Handler.java:44) at org.eclipse.osgi.framework.internal.core.BundleResourceHandler.openConnection(BundleResourceHandler.java:175) at java.net.URL.openConnection(URL.java:945) at org.eclipse.core.internal.boot.PlatformURLConnection.connect(PlatformURLConnection.java:110) at org.eclipse.core.internal.boot.PlatformURLConnection.getURLAsLocal(PlatformURLConnection.java:238) at org.eclipse.core.internal.runtime.PlatformURLConverter.toFileURL(PlatformURLConverter.java:36) at org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:206) at org.eclipse.jface.resource.URLImageDescriptor.getFilePath(URLImageDescriptor.java:137) at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:157) at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:165) at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:56) at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:88) at org.eclipse.jface.resource.LocalResourceManager.allocate(LocalResourceManager.java:82) at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:88) at org.eclipse.jface.resource.ResourceManager.createImage(ResourceManager.java:172) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.getImage(HandledContributionItem.java:598) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.updateIcons(HandledContributionItem.java:571) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.update(HandledContributionItem.java:471) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.update(HandledContributionItem.java:461) at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer$4.handleEvent(MenuManagerRenderer.java:202) On Sat, Oct 13, 2012 at 3:00 AM, <linuxtools-dev-requ...@eclipse.org> wrote: > Send linuxtools-dev mailing list submissions to > linuxtools-dev@eclipse.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev > or, via email, send a message with subject or body 'help' to > linuxtools-dev-requ...@eclipse.org > > You can reach the person managing the list at > linuxtools-dev-ow...@eclipse.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of linuxtools-dev digest..." > > > Today's Topics: > > 1. launching valgrind from CDT crashes on startup > (joc...@bekmann.com) > 2. Re: launching valgrind from CDT crashes on startup > (Roland Grunberg) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 12 Oct 2012 17:33:03 +1100 > From: joc...@bekmann.com > To: linuxtools-dev <linuxtools-dev@eclipse.org> > Subject: [linuxtools-dev] launching valgrind from CDT crashes on > startup > Message-ID: > < > cadr1xrxz2zbhoeojychto+a_cas8yp1hssk-roxgsyzub5u...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all, > > I scoured the eclipse bug database, the eclipse forums and the > linuxtool archives, and haven't seen anything on this. Looks like > ValgrindCommand.java can't read it's version number? > > I can't launch Valgrind from CDT, I get an NPE: > > Id: org.eclipse.linuxtools.valgrind.cachegrind, Version: > 1.0.0.201209191645, Location: > > reference:file:plugins/org.eclipse.linuxtools.valgrind.cachegrind_1.0.0.201209191645.jar > Id: org.eclipse.linuxtools.valgrind.core, Version: 1.0.0.201209191645, > Location: > reference:file:plugins/org.eclipse.linuxtools.valgrind.core_1.0.0.201209191645.jar > Id: org.eclipse.linuxtools.valgrind.doc, Version: 1.0.0.201209191645, > Location: > reference:file:plugins/org.eclipse.linuxtools.valgrind.doc_1.0.0.201209191645.jar > Id: org.eclipse.linuxtools.valgrind.helgrind, Version: > 1.0.0.201209191645, Location: > > reference:file:plugins/org.eclipse.linuxtools.valgrind.helgrind_1.0.0.201209191645.jar > Id: org.eclipse.linuxtools.valgrind.launch, Version: > 1.1.0.201209191645, Location: > > reference:file:plugins/org.eclipse.linuxtools.valgrind.launch_1.1.0.201209191645.jar > Id: org.eclipse.linuxtools.valgrind.massif, Version: > 1.0.0.201209191645, Location: > > reference:file:plugins/org.eclipse.linuxtools.valgrind.massif_1.0.0.201209191645.jar > Id: org.eclipse.linuxtools.valgrind.memcheck, Version: > 1.0.0.201209191645, Location: > > reference:file:plugins/org.eclipse.linuxtools.valgrind.memcheck_1.0.0.201209191645.jar > Id: org.eclipse.linuxtools.valgrind.ui, Version: 1.0.0.201209191645, > Location: > reference:file:plugins/org.eclipse.linuxtools.valgrind.ui_1.0.0.201209191645.jar > Id: org.eclipse.linuxtools.valgrind.ui.editor, Version: > 1.0.0.201209191645, Location: > > reference:file:plugins/org.eclipse.linuxtools.valgrind.ui.editor_1.0.0.201209191645.jar > > eclipse.buildId=M20120914-1800 > java.version=1.6.0_35 > java.vendor=Apple Inc. > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > > > > java.lang.NullPointerException > at > org.eclipse.linuxtools.internal.valgrind.core.ValgrindCommand.readIntoBuffer(ValgrindCommand.java:82) > at > org.eclipse.linuxtools.internal.valgrind.core.ValgrindCommand.whichVersion(ValgrindCommand.java:36) > at > org.eclipse.linuxtools.internal.valgrind.launch.ValgrindLaunchPlugin.getValgrindVersion(ValgrindLaunchPlugin.java:120) > at > org.eclipse.linuxtools.internal.valgrind.launch.ValgrindLaunchConfigurationDelegate.launch(ValgrindLaunchConfigurationDelegate.java:114) > at > org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:855) > at > org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:704) > at > org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1047) > at > org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1251) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > > > and > > java.lang.NullPointerException > at > org.eclipse.linuxtools.internal.valgrind.core.ValgrindCommand.readIntoBuffer(ValgrindCommand.java:82) > at > org.eclipse.linuxtools.internal.valgrind.core.ValgrindCommand.whichVersion(ValgrindCommand.java:36) > at > org.eclipse.linuxtools.internal.valgrind.launch.ValgrindLaunchPlugin.getValgrindVersion(ValgrindLaunchPlugin.java:120) > at > org.eclipse.linuxtools.internal.valgrind.launch.ValgrindOptionsTab.initializeFrom(ValgrindOptionsTab.java:502) > at > org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:86) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.initializeFrom(LaunchConfigurationTabGroupWrapper.java:194) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:753) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:624) > at > org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:641) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:603) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:579) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:941) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:560) > at > org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:888) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) > at > org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:886) > at > org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1726) > at > org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139) > at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:394) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.doInitialTreeSelection(LaunchConfigurationsDialog.java:600) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.initializeContent(LaunchConfigurationsDialog.java:1080) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.createContents(LaunchConfigurationsDialog.java:437) > at org.eclipse.jface.window.Window.create(Window.java:431) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.create(LaunchConfigurationsDialog.java:368) > at org.eclipse.jface.window.Window.open(Window.java:790) > at > org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1132) > at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:600) > at > org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at > org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:608) > at > org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:542) > at > org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:81) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at > org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at > org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at > org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > > > > Is this a known problem? > > thanks, > Jochen > > > ------------------------------ > > Message: 2 > Date: Fri, 12 Oct 2012 10:55:51 -0400 (EDT) > From: Roland Grunberg <rgrun...@redhat.com> > To: Linux Tools developer discussions <linuxtools-dev@eclipse.org> > Subject: Re: [linuxtools-dev] launching valgrind from CDT crashes on > startup > Message-ID: > <1885352330.9969951.1350053751242.javamail.r...@redhat.com> > Content-Type: text/plain; charset=utf-8 > > > I scoured the eclipse bug database, the eclipse forums and the > > linuxtool archives, and haven't seen anything on this. Looks like > > ValgrindCommand.java can't read it's version number? > > > > I can't launch Valgrind from CDT, I get an NPE: > > > > java.lang.NullPointerException > > at > > > org.eclipse.linuxtools.internal.valgrind.core.ValgrindCommand.readIntoBuffer(ValgrindCommand.java:82) > > at > > > org.eclipse.linuxtools.internal.valgrind.core.ValgrindCommand.whichVersion(ValgrindCommand.java:36) > > at > > > org.eclipse.linuxtools.internal.valgrind.launch.ValgrindLaunchPlugin.getValgrindVersion(ValgrindLaunchPlugin.java:120) > > at > > > org.eclipse.linuxtools.internal.valgrind.launch.ValgrindLaunchConfigurationDelegate.launch(ValgrindLaunchConfigurationDelegate.java:114) > > at > > > org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:855) > > at > > > org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:704) > > at > > > org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1047) > > at > > > org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1251) > > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > > > > Looking at the stack trace, it seems like the Process object being created > at ValgrindCommand.java:35 is coming back null. Are there any additional > error messages in the Error Log view around the time this happens (maybe > something mentioning RuntimeProcessFactory) ? > > If not, and given that this seems to be a local launch, I think something > might be going wrong in the CommandLauncher class. The strange thing is > that even the basic things like building a C/C++ project using make rely > on this class. When you build your C/C++ project are there any errors at > all in the error log view ? > > I don't think I've seen something like this before, but if the code is > failing to create a Process object, we should give a better reason for > why this happens. > > -- > Roland Grunberg > > > ------------------------------ > > _______________________________________________ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev > > > End of linuxtools-dev Digest, Vol 45, Issue 8 > ********************************************* >
_______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
