| Avast Security 9.0 blocks debugger port [message #1180746] |
Mon, 11 November 2013 06:01  |
 Gary Worsham
Messages: 176
Registered: September 2013 |
Senior Member |
|
|
[Edit - I changed the topic to reflect the cause of my problems, which took a week to figure out.]
I can't run the debugger on the second instance of Eclipse. Having generated some code from my DSL, I now want to start integrating it with my existing code. It's a lot easier if I can run the debugger.
However I am getting the error:
Launching MyApplication has encountered a problem.
Cannot connect to VM
Details:
Cannot connect to VM
com.sun.jdi.connect.TransportTimeoutException
And in console window it's displayed:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: connect failed: Connection timed out
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
I thought perhaps I could just switch to the generated workspace from the first instance of Kepler. The DSLs would not be active but I'd be able to work with the already-generated code. However, almost all of my generated code does not show up in the project when doing this for some reason. So the Java application won't run at all.
Seems like things are getting weirder and weirder. I did a full reinstall of Eclipse today and it didn't seem to make any difference to any of the problems I've been having.
[Updated on: Thu, 14 November 2013 14:02] Report message to a moderator |
|
|
|
|
|
| Re: Can't run debugger on 2nd instance of Eclipse [message #1181548 is a reply to message #1181393] |
Mon, 11 November 2013 17:24  |
Gary Worsham
Messages: 176
Registered: September 2013 |
Senior Member |
|
|
Christian Dietrich wrote on Mon, 11 November 2013 10:23Hi,
sorry i did not really get your second problem. what do you mean by
"I don't see any of my generated source files from my DSL"
they are there if you do not delete them.
The generated Java files do not show up in Project Explorer and methods are noted as missing cross references when trying to build the project.
[Updated on: Mon, 11 November 2013 17:26] Report message to a moderator |
|
|
|
| Re: Can't run debugger on 2nd instance of Eclipse [message #1182692 is a reply to message #1181558] |
Tue, 12 November 2013 10:54 |
Gary Worsham
Messages: 176
Registered: September 2013 |
Senior Member |
|
|
OK, I double checked, and yes, the files are really there, however they did not appear in Project Explorer until I clicked on File...Refresh. That is the first time in about a year of using Eclipse that I have used that feature! But it did work.
So, I was able to go through all the packages with missing references and refreshed them one by one and all the missing files appeared. So I can start trying to debug my project with only one instance of Eclipse running. I still get the same error.
There is another post on the Eclipse forum indicating this issue has to do with using Avast security software, which I am using.
The same problem is posted over at the Avast forum, apparently by the same user:
http://forum.avast.com/index.php?topic=139390.0
I have attempted to temporarily disable the firewall and file system protection in Avast and it does not help. I get the same error in the console that I pasted earlier. If I choose "show details" on the error dialog, I get this:
Cannot connect to VM
Socket operation on nonsocket: configureBlocking
Where is the setting in Eclipse that controls the debug port?
I'm slightly suspicious about this being the root cause as I am not doing a remote debugging session and it's not clear to me that a software firewall would interfere between applications all running on my local machine.
My case is slightly different in that I have been using Avast security for longer than I've been using Eclipse. However, in the past month that I've been working on my DSLs with Xtext, I have not been using the debugger. There was a major update to Avast that happened within the past few weeks, which I suppose might be the cause.
Thanks,
GW
[Updated on: Tue, 12 November 2013 11:01] Report message to a moderator |
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04973 seconds
] 
Search
Help
Register
Login
Home
