Created attachment 535 [details] hostShellProcess fail The first time, I debug on Host ubuntu x86-64 with target sugarbay(arch is x86-64) succefully, but the second time, i want to debug or run the application, i got error as attachment i encountered with this error before with qemu, but it is not easy to reproduce. The terminal launched eclipse shows: ********************************* org.eclipse.rse.services.clientserver.messages.SystemMessageException: Command [C 138 Terminals launch "vt100" null []] aborted at org.eclipse.tm.internal.tcf.rse.TCFRSETask.getS(TCFRSETask.java:48) at org.eclipse.tm.internal.tcf.rse.shells.TCFTerminalShell.<init>(TCFTerminalShell.java:240) at org.eclipse.tm.internal.tcf.rse.terminals.TCFTerminalService.launchTerminal(TCFTerminalService.java:38) at org.eclipse.rse.internal.services.shells.TerminalShellService.runCommand(TerminalShellService.java:65) at org.eclipse.rse.internal.services.shells.TerminalShellService.launchShell(TerminalShellService.java:53) at org.eclipse.rse.services.shells.AbstractShellService.launchShell(AbstractShellService.java:46) at org.eclipse.cdt.launch.remote.RSEHelper.remoteShellExec(RSEHelper.java:266) at org.eclipse.cdt.launch.remote.launching.RemoteRunLaunchDelegate.launch(RemoteRunLaunchDelegate.java:129) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) ********************************* The steps are below: 1.install meta-toolchain.(http://autobuilder.pokylinux.org/pub/nightly/20120523-2/toolchain/x86-64/poky-eglibc-x86_64-x86_64-toolchain-gmae-1.2+snapshot-20120523.tar.bz2) 2.In eclipse, Windows -> Preferences -> Yocto ADT set /opt/poky/1.2+snapshot directory as Toolchain Root Location,Specify the Sysroot Location as /opt/poky/1.2+snapshot/sysroot. 3.New a project based on Yocto ADT Project/Hello World ANSI C Autotools Project. 4.Build the project, and right click the project select Dubug as-> Debug configuration, in left menu it will generate a configuration named {ProjectName}_gdb_x86_64-poky-linux, In tab main window, New a connection->TCF, in HOST name field input the remote machine's IP, make sure your connection is this IP address, cause default value is local. 5.The field "Remote Absolute File Path for C/C++ Application", i input /home/root/hello 6.make sure in Debugger tab, my values are: GDB debugger:/opt/poky/1.2+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gdb GDB command file:/home/xuhongna/eclipse/workspaceNew/hello/.gdbinit If yours are not, please new a new project to debug or manual edit them. If you get the warning, the file doesn;t exist, after the above settings, rebuild the project then debug it. 7.In tab main window, click"Select other.." to change launcher, we can use two launchers in our project, they are GDB(DFS)Automantic Remote Dubugging Launcher and Standard Remote Create Process Launcher(default). git info: 094742bed2fc01d55f572da946fcfa7a48521401 git branch: poky/master
Sugarbya image location: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120531-1/machines/sugarbay/ core-image-sato-sdk-sugarbay-20120531005900.hddimg
the root cause of this bug is in function org.eclipse.tm.internal.tcf.rse.shells.TCFTerminalShell$1.exited(). A nullpointer exception would be raised at the line of "if(!terminalContext.getID().equals(terminalId))", when another tcf terminal exit event is sent in here before the current terminal is actually created. I'll lower this bug priority because we're trying to replace tcf by RSE/SSH now.
The upstream TCF 1.0 has fixed this issue in commmit http://git.eclipse.org/c/tcf/org.eclipse.tcf.git/commit/?id=1a0485cdbbf014f03d9466fd84fdd51514466a1f.
closing