Lines Matching refs:jdb
36 # and use jdb as the debugger. This file contains
97 # There are problem with jtreg leaving behind orphan java and jdb processes
101 # and jdb processes this script launches. We can then do the right kind
114 # of using $! to get the PIDs of the jdb and debuggee processes
120 # resort to just killing java.exe and jdb.exes
123 # debuggeepid: used in jdb process to detect if debuggee has died.
126 # jdbpid: dofail: used to detect if in main process or jdb process
127 # waitforfinish: quit if the jdb process is gone
140 # cmds to jdb, then stdout is redirected to jdb.
225 # This is used to tag each java and jdb cmd we issue so
257 jdbKeyword='jdb\.exe'
334 # This must not contain 'jdb' or it shows up
366 if [ -z "$jdb" ] ; then
367 jdb=$jdk/bin/jdb
516 # Send a cmd to jdb and wait for the jdb prompt to appear.
518 # runs for awhile after a command, jdb will show this prompt
521 # If it ever becomes necessary to send a jdb command before
527 # if jdb got a cont cmd that caused the debuggee
528 # to run to completion, jdb can be gone before
533 # can cause jdb to not get the quit.
543 # because after starting jdb, we waited
549 # It is as if every so often, jdb doesn't
553 # It seems like jdb really doesn't get the cmd; jdb's response
559 # that jdb got the cmd ok, but its response didn't make
566 # Also, the cmd is shown in the 'jdb never responded ...'
568 # And, we know jdb is started because the main[1] output is in the .jtr
573 # Now we have to wait for the next jdb prompt. We wait for a pattern
574 # to appear in the last line of jdb output. Normally, the prompt is
580 # the following jdb output can appear:
588 # This occurs if the next cmd is one that causes no jdb output, e.g.,
593 # jdb prints a > as a prompt after something like a cont.
642 # wait for 4 new chars to appear in the jdb output
658 echo "--DEBUG: jdb $$ didn't responded to command in $count secs: $*" >& 2
667 dofail "jdb never responded to command: $*"
691 # Wait for jdb to hit the bkpt
700 # Wait for jdb to hit the bkpt
706 # If $3 is allowExit, then don't fail if jdb exits before
710 # This can be called from the jdb thread which doesn't
715 timeLimit=40 # wait a max of this many secs for a response from a jdb command
718 # Something here causes jdb to complain about Unrecognized cmd on x86.
738 dofail "Waited for jdb msg $1, but it never appeared"
768 # we are in the main process instead of the jdb process
806 # Wait for jdb to start before we start sending cmds
814 if [ ! -r "$jdb" -a ! -r "$jdb.exe" ] ; then
815 dofail "$jdb does not exist"
818 echo "--Starting jdb, address=$address"
820 # Let jdb choose the port and write it to stdout
821 mydojdbCmds | $jdb $jdbOptions -listenany | tee $jdbOutFile &
833 mydojdbCmds | $jdb $jdbOptions -listen $address | tee $jdbOutFile &
841 # This fails on linux because there is an entry for each thread in jdb
880 # Save this in a place where the jdb process can find it.
890 # Show stack traces of jdb and debuggee as a possible debugging aid.
894 echo "-- jdb process info ----------------------" >&2
896 echo "-- jdb threads: jstack $realJdbPid" >&2
925 # Wait for the jdb process to finish, or some error to occur
941 dofail "jdb input stream closed prematurely"
992 # See bug 6220903. Sometimes the jdb prompt chars ('> ') can
1033 # fail if $1 is not in the jdb output
1047 # fail if $1 is in the jdb output