Skip to main content
Jump to: navigation, search

Difference between revisions of "Debug/FAQ"

Line 36: Line 36:
     JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
     JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized

Revision as of 15:22, 4 October 2007


How do I contribute to this FAQ?


How can I help out the Debug Team?



What is contextual launching?





How do I turn off contextual launching?


I can run a program but not debug it???


    JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized



          # Do not remove the following line, or various programs
          # that require network functionality will fail.
          ::1     localhost.localdomain   localhost
  3. If you have edited the environment to use for launching on the 'Environment' tab in the launch dialog, and have selected the 'replace my environment' option on the bottom, you must ensure that the variable you specify in the listing are sufficient for launching. More specifically, you have to include all of the environment varibales that your system and eclipse needs to launch. The safest course of action when you want select the 'replace my environment' is to add all of the variables and your own, and to only remove those which you know for a fact are not required by your system or Eclipse.
  4. It could be that there is some garbage text in your environment. To find out try typing either
    cmd.exe /C set (in Windows)
    env (in Linux or Mac)
    . The output produced should look like the following, where there are variables followed by an '=', followed by the value of the variable.
    If there is garbage text in this output you need to clean up your system variables, otherwise the debugger cannot parse your environment. The other solution to this is to migrate to using Eclipse 3.3.1 or newer, where we added support for ignoring garbage text you environment.
  5. If you have the JRE you wish to use for launching installed in a jdk path, the debugger will not start complaining about it inability to find system libraries. For example, lets say you have Java 6 installed in C:\java\jdk6. Now lets say that in Eclipse you have your default JRE (the one you want to use for launching) set to the installed path C:\java\jdk6. Pre-3.3.1 debugging will not work because we would scan the current directory to find the system libraries needed to debug, and find none. The problem was that we were not correctly appending paths in our debugger to find the system libraries in the JRE folder of the install location. This has been fixed in Eclipse 3.3.1.

Java Debugging



What is hyper-link debugging?







Variables View

What are logical structures?


What are detail formatters?


What is the detail pane?








Back to the top