Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315751 - [terminal][local] UnsatisfiedLinkError printed to stdout when CDT does not have a native spawner lib
Summary: [terminal][local] UnsatisfiedLinkError printed to stdout when CDT does not ha...
Status: RESOLVED DUPLICATE of bug 314977
Alias: None
Product: Target Management
Classification: Tools
Component: Terminal (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: dsdp.tm.core-inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-04 07:37 EDT by Martin Oberhuber CLA
Modified: 2010-06-04 12:10 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2010-06-04 07:37:02 EDT 
Build ID: TM 3.2rc3

When trying to verify the fix for bug 315124 on Solaris, I got into a situation where cdt.core was installed but the cdt.core.solaris fragment was not. The same might happen on AIX or HPUX. I got the following traceback printed to stdout:

java.lang.UnsatisfiedLinkError: no spawner in java.library.path
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
        at java.lang.Runtime.loadLibrary0(Runtime.java:822)
        at java.lang.System.loadLibrary(System.java:992)
        at org.eclipse.cdt.utils.spawner.ProcessFactory.<init>(ProcessFactory.java:39)
        at org.eclipse.cdt.utils.spawner.ProcessFactory.getFactory(ProcessFactory.java:51)
        at org.eclipse.tm.internal.terminal.local.launch.LocalTerminalLaunchDelegate.launch(LocalTerminalLaunchDelegate.java:161)
        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.core.LaunchConfiguration.launch(LaunchConfiguration.java:695)
        at org.eclipse.tm.internal.terminal.local.LocalTerminalConnector.connect(LocalTerminalConnector.java:212)
        at org.eclipse.tm.internal.terminal.connector.TerminalConnector.connect(TerminalConnector.java:159)
        at org.eclipse.tm.internal.terminal.emulator.VT100TerminalControl.connectTerminal(VT100TerminalControl.java:318)
        at org.eclipse.tm.internal.terminal.view.TerminalView.onTerminalConnect(TerminalView.java:294)
        at org.eclipse.tm.internal.terminal.view.TerminalView.newConnection(TerminalView.java:334)
        at org.eclipse.tm.internal.terminal.view.TerminalView.onTerminalSettings(TerminalView.java:327)
        at org.eclipse.tm.internal.terminal.actions.TerminalActionSettings.run(TerminalActionSettings.java:37)
        at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
        at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
Comment 1 Martin Oberhuber CLA 2010-06-04 07:38:19 EDT 
Expected behavior: Show an error message in this case and disable the local terminal functionality. This might actually be fixed by the patch on 
bug 314977 comment 3.
Comment 2 Martin Oberhuber CLA 2010-06-04 12:10:38 EDT 
This has actually been resolved with bug 314977.

*** This bug has been marked as a duplicate of bug 314977 ***