官术网_书友最值得收藏!

Time for action – updating code in the debugger

When an Eclipse instance is launched in run mode, changes made to the source code aren't reflected in the running instance. However, debug mode allows changes made to the source to be reflected in the running target Eclipse instance.

  1. Launch the target Eclipse in debug mode by clicking on the debug icon.
  2. Click on the hello world icon in the target Eclipse to display the dialog, as before, and click on OK to dismiss it. It may be necessary to remove or resume the breakpoint in the host Eclipse instance to allow execution to continue.
  3. In the host Eclipse, open the SampleHandler class and go to the execute method.
  4. Change the title of the dialog to Hello again, Eclipse world and save the file. Provided the Build Automatically option in Project menu is enabled, the change will be automatically recompiled.
  5. Click on the hello world icon in the target Eclipse instance again. The new message should be shown.

What just happened?

By default, Eclipse ships with the Build Automatically option in Project menu enabled. Whenever changes are made to Java files, they are recompiled along with their dependencies if necessary.

When a Java program is launched in run mode, it will load classes on demand and then keep using that definition until the JVM shuts down. Even if the classes are changed, the JVM won't notice that they have been updated, and so no differences will be seen in the running application.

However, when a Java program is launched in debug mode, whenever changes to classes are made, Eclipse will update the running JVM with the new code if possible. The limits to what can be replaced are controlled by the JVM through the Java Virtual Machine Tools Interface (JVMTI). Generally, updating an existing method and adding a new method or field will work, but changes to interfaces and superclasses may not be.

Note

The Hotspot JVM cannot replace classes if methods are added or interfaces are updated. Some JVMs have additional capabilities that can substitute more code on demand. Other JVMs, such as IBM's, can deal with a wider range of replacements.

Note that there are some types of changes that won't be picked up, for example, new extensions added to the plugin.xml file. In order to see these changes, it is possible to start and stop the plug-in through the command-line OSGi console, or restart Eclipse inside or outside of the host Eclipse to see the change.

Debugging with step filters

When debugging using Step Into, the code will frequently go into Java internals, such as the implementation of Java collections classes or other internal JVM classes. These don't usually add value, so fortunately Eclipse has a way of ignoring uninteresting classes.

主站蜘蛛池模板: 泸州市| 潼关县| 荣成市| 乌鲁木齐市| 鄂尔多斯市| 乐亭县| 仪陇县| 仪征市| 灵武市| 错那县| 壶关县| 北辰区| 云阳县| 綦江县| 宁城县| 宜春市| 合江县| 咸阳市| 余姚市| 潮州市| 林芝县| 彰化县| 桃园县| 张家口市| 滨海县| 霍林郭勒市| 繁峙县| 拜泉县| 遵义县| 綦江县| 齐齐哈尔市| 鹤山市| 莒南县| 余姚市| 亚东县| 京山县| 锦州市| 遂溪县| 沁源县| 阳东县| 松江区|