How do I get rid of this when I try to start debugging?
I have a startKIT. I have tried "everything". Some times debugging starts.
xTIMEcomposer 14.0.4 but also 14.1.0. The latter I have given up at the time, and gone back tp 14.0.4. It seems like I took the socket binding error with me, because I haven't seen it before on 14.0.4.
I have OS X 10.10.5. JRE 1.8.0_51
I have shown some of it here.
ERROR: socket bind.(0)
-
aclassifier
- Respected Member
- Posts: 487
- Joined: Wed Apr 25, 2012 8:52 pm
-
xmark
- Member++
- Posts: 19
- Joined: Mon Apr 26, 2010 2:35 pm
Hi,
I had this issue today for the first time. In my case, a reboot returned my machine to normality.
-Mark
I had this issue today for the first time. In my case, a reboot returned my machine to normality.
-Mark
-
andrewxcav
- Active Member
- Posts: 62
- Joined: Wed Feb 17, 2016 5:10 pm
Same problem here on Fedora 23
Tools Version: Community_14.2.0 (build 11257, May-12-2016)
java version "1.8.0_77"
Rebooting fixed it as well.
Possibly relevant post about Java socket bind errors:
http://stackoverflow.com/questions/1085 ... bind-error
Tools Version: Community_14.2.0 (build 11257, May-12-2016)
java version "1.8.0_77"
Rebooting fixed it as well.
Possibly relevant post about Java socket bind errors:
http://stackoverflow.com/questions/1085 ... bind-error
-
infiniteimprobability
- XCore Legend
- Posts: 1126
- Joined: Thu May 27, 2010 10:08 am
Similar issue for me (first time ever after thousands of xruns..). However ps revealed xrun and xgdb hadn't terminated on ctrl-c. Killed those processes and all was well again..