This page describes limitations that you may encounter when debugging
mixed languages and suggested methods for working around those limitations.
Please also see the product readme, which may contain additional limitations
for this debugger.
- Drop to frame and Hot code replace: Do not use the drop to frame
and hot code replace features while debugging other languages called from Java™.
- Suspending all Java breakpoints: Do not suspend all Java breakpoints
when debugging mixed language applications.
- Step over and step return: Step over and step return are only supported
for the top stack frame.
- Suspending: Suspend might not work properly when debugging a mixed
language application. Use breakpoints instead.
Hot Method Replace
- Changes to source that affect the shape of the class are not supported.
This means that changes to method bodies will be hot replaced, while these
are examples of changes that will not be hot replaced:
- changes to class structure, such as the removal/addition of methods
- modification of class variables
- changes to inner classes
- Changes to the code in the bottom stack frame (the main(...) method)
cannot be hot replaced.
- JSP page debugging does not support hot method replace of Java code.