###@###.### 2002-04-26
The JPDA backend currenty uses temporary BREAKPOINT events to cause
BREAKPOINT and SINGLE_STEP events at the same location to be in the
same event set. In HotSpot, setting and clearing a BREAKPOINT is
done via a VM operation which is done during a safepoint. This isn't
a problem with just a few threads, but doesn't scale well when you
have a lot of threads.
This logic was originally added with the following bug fix:
4195505 4/3 JVMDI: Breakpoints not reported when stepping
This change should be done with the HotSpot work being done via:
4478469 4/2 single stepping with lots of Java threads is very slow
The JPDA backend currenty uses temporary BREAKPOINT events to cause
BREAKPOINT and SINGLE_STEP events at the same location to be in the
same event set. In HotSpot, setting and clearing a BREAKPOINT is
done via a VM operation which is done during a safepoint. This isn't
a problem with just a few threads, but doesn't scale well when you
have a lot of threads.
This logic was originally added with the following bug fix:
4195505 4/3 JVMDI: Breakpoints not reported when stepping
This change should be done with the HotSpot work being done via:
4478469 4/2 single stepping with lots of Java threads is very slow
- relates to
-
JDK-4195505 JVMDI: Breakpoints not reported when stepping
-
- Closed
-
-
JDK-4416804 jdb in 1.3 is 6.5 times slower than 1.2
-
- Closed
-
-
JDK-4478469 single stepping with lots of Java threads is very slow
-
- Resolved
-