Created attachment 621 [details] deploy to remote target if i want to connect to qemuarm/mips/ppc/x86/x86-64 sato sdk image first time in eclipse, i encounter the file system null error as attachment, but when i try for the second time, it would connect to target. the image location:http://autobuilder.yoctoproject.org/pub/nightly/20120613-1/machines/qemu/, built from poky/master,commitID 7f017cab0b3e4d5a4fc356eccd8eb8429b0531d0
Created attachment 622 [details] the tool of oprofile connecting to target
To reproduce this issue, we need an abnormal usage scenario. 1. Launch a qemu instance and use the Eclipse to connect to it on a TCF connection. So an underlying tcp connection was established between the host and the qemu target. 2. Directly kill the qemu instance. The underlying tcp connection was still in ESTABLISHED state since there is no FIN tcp segment ever exchanged between the host and the target, and the default system tcp_keepalive_time is set to 20 minutes so the system can not detect it until then. 3. Launch a new qemu instance, and try to redo the operations in step 1 again. The RSE/TCF subsystem thinks the TCF connection is still in a valid connected status, so it will directly send the data on that connection. However on the target qemu side, there is no such a TCP connection so it would result an error we see in Hongna's screen shot and it would cause the host tcp connection to be invalidated. So if the user tries for the second time, the RSE/TCF subsystem would reconnect and succeed. If the qemu is correctly shutdown, the RSE/TCF subsystem would get notified of the connection shutdown event and handle it properly.
thank you for lianhao's clarification. but i use the same way to test in previous testing, i encounter this issue for most 2-3 times before in all, but now it happens frequently, why? do they change the socket communication mechanism? i don't think so, what expose it?
the issue seems gone on 1.3M2rc1 testing. Tree/Branch: poky/master Commit id: eb0cb7e8234f5d2e5623406e9660be91cf52f65e plugin location:http://autobuilder.pokylinux.org/pub/nightly/20120712-1/eclipse-plugin/indigo/ image location: http://autobuilder.pokylinux.org/pub/nightly/20120712-1/machines/qemu/
change the status per last comments, maybe reopened if run into it again
> change the status per last comments, maybe reopened if run into it again Hi, I managed to reproduce the issue Hongna found following Linhao's scenario when trying to run PowerTop. I have tested installing Eclipse, adt using 1.3_M4 RC3: e5c3513ca8abb21eb5e9b8c19d1b9199b14ae07c
We are moving away from TCF connection overall
Marking this as verified. TCF is not present in Kepler and from the above comments it seems that will be dropped.