Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
View | Details | Raw Unified | Return to bug 185753 | Differences between
and this patch

Collapse All | Expand All

(-)rootfiles/readme/readme_eclipse.html (-6 lines)
Lines 1121-1132 Link Here
1121
  execution in a specific class, execution will still suspend when the user preference 
1121
  execution in a specific class, execution will still suspend when the user preference 
1122
  to suspend on uncaught exceptions is on. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66770">66770</a>)</p>
1122
  to suspend on uncaught exceptions is on. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=66770">66770</a>)</p>
1123
1123
1124
<h4>Debugger cannot connect when Eclipse runs on IBM JRE 5.0</h4>
1125
<p>When Eclipse is running on IBM JRE 5.0, the debugger cannot connect to other 
1126
  VMs for the purpose of debugging. The IBM JRE 5.0 prepends its bin directory 
1127
  to the system path such that the other VMs do not find their required compatible 
1128
  libraries required for debugging. (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=128605">128605</a>) 
1129
</p>
1130
<h4>Running Java programs with non-Latin-1 characters in package or class names</h4>
1124
<h4>Running Java programs with non-Latin-1 characters in package or class names</h4>
1131
You get a <code>java.lang.NoClassDefFoundError</code> when running Java
1125
You get a <code>java.lang.NoClassDefFoundError</code> when running Java
1132
programs with non-Latin characters in the package or class names. The workaround
1126
programs with non-Latin characters in the package or class names. The workaround

Return to bug 185753