eclipse-tptp - 如何在 Windows 中绕过 TPTP 的 IWAT0435E

Question

我刚刚安装了 TPTP 的最新版本 (4.6.1) 并在 Windows 7(启用用户控制)上使用 Eclipse build 20090621-0832。
我正在尝试分析应用程序，但在“监视器”选项卡下收到以下错误:

IWAT0435E An error occurred when connecting to the host.

有人知道怎么解决吗？

Answer 1

对于 Windows，这可能与缺少对 Integrated Agent Controller (IAC) 的引用有关

The Integrated Agent Controller (IAC) is a new feature in TPTP workbench which allows users to profile a Java application locally and to run a TPTP Test locally without needing the standalone Agent Controller on the local machine.
Profiling on a remote machine or running a TPTP test on a remote machine would still need the Agent Controller on that remote machine.
The biggest benefit of the Integrated Agent Controller is that it simplifies the usage of TPTP functionality in the local scenario by removing the dependency on the local standalone Agent Controller. There is no need to install and configure the local standalone Agent Controller when using the Profiling and Logging perspective and Test perspective locally.

但是，在其中一个 TPTP 配置文件中可能未正确引用该本地代理，原因可能是:

• 是already referenced in the workspace (错误地)
  请参见 workspace\.metadata\.plugins\org.eclipse.tptp.platform.iac.administrator\config\serviceconfig.xml
• 或者因为IAC服务没有自动启动:
  检查与本地主机的连接(通过 Window->preferences->Agent Controller->hosts->Test connection)。
  参见 this thread (及其后续行动)用于工作设置。

This thread也可能相关。

---

对于 Linux 用户:

可能与gcc版本或libstdc++xx-glibcy.y版本有关，在bug 244213中提到或 bug 240677

这blog post涉及在他的情况下可能采用哪种解决方法。也许它可以在这里有所帮助。

---

摘录:

A workaround for this is described in this blog post.

It's pretty straight forward: get a deb file libstdc++2.10-glibc2.2_2.95.4-27_i386.deb and install it with sudo dpkg ....

(2010 年 12 月更新:3.x 之前的 gcc 不再可用。
例如，您可以尝试使用 (gcc-3.3) libstdc++5_3.3.6-20_i386.deb , 用这个替换所有对 .deb 的引用:

sudo dpkg --install libstdc++5_3.3.6-20_i386.deb

或者如果您在 64 位上运行:

sudo dpkg --force-architecture --install libstdc++5_3.3.6-20_i386.deb

虽然没有测试。)

The problem is now that the workaround involves root actions.
First, one hasn't always the required root permissions to do so.
More importantly however, I don't like installing external debs and other stuff as root because it can interfere with the packaging system, pollute system directories and break things in ugly, or worse, unrecoverable ways.

I always install third party stuff (with which I mean things that are not available through the standard packaging system) in my home directory under ~/usr.
For example, I build autotools-managed software with the option --prefix=~/usr, so things end up in ~/usr/bin, ~/usr/lib, ~/usr/share, etcetera.

I managed to install the deb file described above also in ~/usr as follows.
First, I extracted the deb file to a temporary directory to get an idea of its contents:

dpkg -x libstdc++2.10-glibc2.2_2.95.4-27_i386.deb tmp/

This resulted in the following file tree:

tmp/
`-- usr
    |-- lib
    |   |-- libstdc++-3-libc6.2-2-2.10.0.so
    |   `-- libstdc++-libc6.2-2.so.3 -> libstdc++-3-libc6.2-2-2.10.0.so
    `-- share
        `-- doc
            `-- libstdc++2.10-glibc2.2
                |-- README.Bugs.gz
                |-- README.Debian
                |-- changelog.Debian.gz
                `-- copyright

So I just had to move the shared libraries libstdc++*.so to ~/usr/lib, or alternatively, extract the deb file directly int my home directory:

dpkg -x libstdc++2.10-glibc2.2_2.95.4-27_i386.deb ~/

One important missing piece of the puzzle is to make sure these shared libraries can be found at run time (or compile time in case you want to compile against them).
The trick is to set the LD_LIBRARY_PATH and LD_RUN_PATH environment variables, typically in your ~/.bashrc or ~/.profile startup scripts:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:~/usr/lib
export LD_LIBRARY_PATH
LD_RUN_PATH=$LD_RUN_PATH:~/usr/lib
export LD_RUN_PATH

And Eclipse TPTP profiling lived happily ever after. I hope.