-
Enhancement
-
Resolution: Won't Fix
-
P4
-
1.4.2
-
generic
-
generic
Name: dkR10014 Date: 12/20/2002
I found that only commands that do not affects an execution point in
debugee can be used in the 'read' command file because batch commands
are executed asynchronously in it. It is almost impossible to use the
commands like 'cont' and 'step' in interaction with others in command
file because of undefined execution point.
Another mode of this command (or another command) should exist in case
when next command should not be executed before a completion of previous
one. This could help much in typical debug scenario like:
stop at ... - set breakpoint at a point where debugee will be in
desired state;
cont - resume debugee;
wait until the breakpoint is hit;
eval <expr> - check an assertion.
...
======================================================================
I found that only commands that do not affects an execution point in
debugee can be used in the 'read' command file because batch commands
are executed asynchronously in it. It is almost impossible to use the
commands like 'cont' and 'step' in interaction with others in command
file because of undefined execution point.
Another mode of this command (or another command) should exist in case
when next command should not be executed before a completion of previous
one. This could help much in typical debug scenario like:
stop at ... - set breakpoint at a point where debugee will be in
desired state;
cont - resume debugee;
wait until the breakpoint is hit;
eval <expr> - check an assertion.
...
======================================================================
- relates to
-
JDK-6220903 TTY: Race in printing prompt and printing output in the event handler
-
- Closed
-