| Re: [tcf-dev] Stack overflow when launching debug session |
Hi Eugene. Thanks – that’s all good information. In particular – I didn’t realize that there was a vanilla TCF launch available. I tried it and it works! As for my doubts about Xilinx – the only response I’ve had to my inquiry there is to be asked if I get the same error message from Vivado. In case you’re not familiar with it, Vivado is Xilinx’s VHDL/Verilog design tool. It has nothing to do with Eclipse, software or TCF. At any rate, you’ve saved me what would undoubtedly have been hours of frustration – thank you again! -Nick From: Eugene Tarassov - eugene.tarassov@xxxxxxxxxx [mailto:tcf-dev.orinc.9cd400b1ba.eugene.tarassov#xilinx.com@xxxxxxxxxx] Hi Nick, TCF is part of standard Eclipse, but it is not installed by default. You can install it using Help / Install New Software / All Available Sites / Mobile and Device Development / TCF C/C++ Debugger. Also, you might be able to workaround the error in Xilinx SDK if you use original TCF launch configuration to start debug session, instead of proprietary Xilinx launch. And, it looks like the launch broke down after you moved files between projects, so re-importing project into a clean workspace might also fix it. Or just deleting and re-creating the launch config might be sufficient. > I’m not hopeful that I’ll be able to get anything out of Xilinx without paying for it… Good bug reports are very valuable. They should be grateful regardless of where the report is coming from. Regards, Eugene From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of tcf-dev.1.orinc@xxxxxxxxxxxxxxx Hi Eugene. Thanks. I’m not hopeful that I’ll be able to get anything out of Xilinx without paying for it. I tried the 2016.3 version of the SDK, but that brought along its own set of problems, not the least of which is an upgrade to version 5 of GCC. That version uses a different ABI for the C++11 bits, but even disabling the new ABI, I’m left with inexplicable compilation errors. If I’m unable to resolve my problems with Xilinx, is TCF a part of standard Eclipse CDT, or does it need to be added as a plug-in? Thanks again, -Nick From: Eugene Tarassov - eugene.tarassov@xxxxxxxxxx [mailto:tcf-dev.orinc.9cd400b1ba.eugene.tarassov#xilinx.com@xxxxxxxxxx] Hi Nick, According to the stack trace, offending code in not part of Eclipse TCF. It is Xilinx extension, owned by Xilinx SDK team. You have to contact them through Xilinx customer support channels, for example, using Xilinx Community Forums. Also, I suggest to try latest SDK version, 2016.3. BTW, cross-platform development for Ubuntu on 32-bit ARM is possible with plain vanilla Eclipse, Xilinx SDK is not really needed for that. Regards, Eugene From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of tcf-dev.1.orinc@xxxxxxxxxxxxxxx Hi All. In brief - I’ve encountered a fatal error while attempting to launch a TCF remote debugging session. I get a stack overflow from Eclipse. The .log file contains this error, which explains the stack overflow: !ENTRY org.eclipse.core.jobs 4 2 2016-11-29 16:38:36.504 !MESSAGE An internal error occurred during: "Launching XXXXXXXX". !STACK 0 java.lang.StackOverflowError at org.eclipse.core.internal.dtree.DeltaDataTree.lookup(DeltaDataTree.java:682) at org.eclipse.core.internal.watson.ElementTree.includes(ElementTree.java:529) at org.eclipse.core.internal.resources.Workspace.getResourceInfo(Workspace.java:1698) at org.eclipse.core.internal.resources.Resource.getResourceInfo(Resource.java:1201) at org.eclipse.core.internal.resources.Project.getReferencedProjects(Project.java:468) at com.xilinx.sdk.tcf.debug.launch.XilinxTCFLaunchDelegate.addToBuildOrder(XilinxTCFLaunchDelegate.java:247) at com.xilinx.sdk.tcf.debug.launch.XilinxTCFLaunchDelegate.addToBuildOrder(XilinxTCFLaunchDelegate.java:249) at com.xilinx.sdk.tcf.debug.launch.XilinxTCFLaunchDelegate.addToBuildOrder(XilinxTCFLaunchDelegate.java:249) at com.xilinx.sdk.tcf.debug.launch.XilinxTCFLaunchDelegate.addToBuildOrder(XilinxTCFLaunchDelegate.java:249) at com.xilinx.sdk.tcf.debug.launch.XilinxTCFLaunchDelegate.addToBuildOrder(XilinxTCFLaunchDelegate.java:249) at com.xilinx.sdk.tcf.debug.launch.XilinxTCFLaunchDelegate.addToBuildOrder(XilinxTCFLaunchDelegate.java:249) at com.xilinx.sdk.tcf.debug.launch.XilinxTCFLaunchDelegate.addToBuildOrder(XilinxTCFLaunchDelegate.java:249) [1000+ identical lines skipped] followed by this error: !ENTRY org.eclipse.tcf 4 0 2016-11-30 12:48:32.182 !MESSAGE TCF channel terminated !STACK 0 java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:209) at java.net.SocketInputStream.read(SocketInputStream.java:141) at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) at java.io.BufferedInputStream.read(BufferedInputStream.java:345) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.eclipse.tcf.core.ChannelTCP.get(ChannelTCP.java:162) at org.eclipse.tcf.core.StreamChannel.read(StreamChannel.java:84) at org.eclipse.tcf.core.AbstractChannel$1.run(AbstractChannel.java:254) and finally a dialog suggesting that it’s time to exit Eclipse. This setup has been working for many months. It worked earlier in the day. I move a couple of files between projects (not suggesting that’s significant, though), and now one of the two executable projects fails like this – the other is still working fine. I’m using the Xilinx SDK 2016.1 (Eclipse 4.5, CDT 8.8) on Windows 10, doing cross-platform development for Ubuntu 14.4 on 32-bit ARM. I’ve been using the TCF agent pulled from git on 24 June. Help? -Nick
|