Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » Java Development Tools (JDT) » Debugging instrumented code
Debugging instrumented code [message #1806396] Wed, 08 May 2019 12:32 Go to next message
Edmundo López Bóbeda is currently offline Edmundo López BóbedaFriend
Messages: 27
Registered: October 2012
Junior Member
Hello,

I'm trying to debug some code and I cannot see the variables view, I get a:

com.sun.jdi.InternalException: Got error code in reply:35

instead of the variables. This was a remote debugging session. After a whileI found that it all worked when I deactivated the instrumentation of the code that was happening in the remote JVM.

My question is, how can I ensure that instrumented code is "debuggable" and that it appears correctly in the Variables section of the eclipse debugger?

Best regards,

Edmundo
Re: Debugging instrumented code [message #1806539 is a reply to message #1806396] Fri, 10 May 2019 09:13 Go to previous messageGo to next message
Sarika Sinha is currently offline Sarika SinhaFriend
Messages: 131
Registered: February 2010
Location: Bangalore, India
Senior Member
Try changing suspend=n to suspend=y to let it wait until you attach the debugger.

Sarika Sinha
JDT Programmer
Re: Debugging instrumented code [message #1806587 is a reply to message #1806539] Fri, 10 May 2019 22:52 Go to previous messageGo to next message
Edmundo López Bóbeda is currently offline Edmundo López BóbedaFriend
Messages: 27
Registered: October 2012
Junior Member
Thanks for your answer, where do I change that setting?
Re: Debugging instrumented code [message #1806589 is a reply to message #1806587] Sat, 11 May 2019 03:57 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33133
Registered: July 2009
Senior Member
When you launched the remote JVM you must have used options like
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8123
so that you could attach to it, right? The suspend "argument" tells the process whether to wait/suspend until the remote debugger is attached or whether to start running immediately. Without such an option you could never debug startup/initialization logic...


Ed Merks
Professional Support: https://www.macromodeling.com/
Re: Debugging instrumented code [message #1806603 is a reply to message #1806589] Sat, 11 May 2019 12:19 Go to previous message
Edmundo López Bóbeda is currently offline Edmundo López BóbedaFriend
Messages: 27
Registered: October 2012
Junior Member
Thank you, I'll try that one.
Previous Topic:Java development tools
Next Topic:Why is the Debug Shell not letting me display valid variables?
Goto Forum:
  


Current Time: Thu Apr 18 10:54:50 GMT 2024

Powered by FUDForum. Page generated in 0.02140 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top