#!/bin/sh

#

# Copyright (c) 2002, 2010, Oracle and/or its affiliates. All rights reserved.

# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.

#

# This code is free software; you can redistribute it and/or modify it

# under the terms of the GNU General Public License version 2 only, as

# published by the Free Software Foundation.

#

# This code is distributed in the hope that it will be useful, but WITHOUT

# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or

# FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License

# version 2 for more details (a copy is included in the LICENSE file that

# accompanied this code).

#

# You should have received a copy of the GNU General Public License version

# 2 along with this work; if not, write to the Free Software Foundation,

# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.

#

# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA

# or visit www.oracle.com if you need additional information or have any

# questions.

#

#

#

# jtreg runs this in a scratch dir.

# It (and runregress -no) sets these env vars:

#    TESTSRC:      The dir that contains this file

#    TESTCLASSES:  Where .class files are compiled to

#    TESTJAVA:     The jdk to run

#

# This is a 'library' script that is included by

# shell script test cases that want to run a .java file as the debuggee

# and use jdb as the debugger.  This file contains

# several functions that support such a test.

# The caller script can also set these shell vars before

# including this file:

#    pkg=<package name>       To use a package, define it here and put

#                                package $pkg

#                             in your java file

#    classname=<classnam>     Omit this to use the default class name, 'shtest'.

#    compileOptions=<string>  compile options for at least the first compile, 

#                             eg, compileOptions=-g

#    compileOptions2=<string> Options for the 2nd, ..., compile. compileOptions1

#                             is used if this is not set.  To use no compile

#                             options for the 2nd ... compiles, do 

#                             compileOptions2=none

#

#    mode=-Xcomp or mode=-Xint to run in these modes.  These should not

#                              really be used since the tests are normally

#                              run in both modes.

#    javacCmd=path-to-javac    to use a non-standard javac for compiling

#    compileOptions=<string>   Options to pass to javac

#

# See RedefineException.sh as an example of a caller script.

#

# To do RedefineClasses operations, embed @1 tags in the .java

# file to tell this script how to modify it to produce the 2nd

# version of the .class file to be used in the redefine operation.

# Here are examples of each editting tag and what change

# it causes in the new file.  Note that blanks are not preserved

# in these editing operations.

#

# @1 uncomment

#  orig:   // @1 uncomment   gus = 89;

#  new:         gus = 89;

#

# @1 commentout

#  orig:   gus = 89      // @1 commentout

#  new: // gus = 89      // @1 commentout

#

# @1 delete

#  orig:  gus = 89      // @1 delete

#  new:   entire line deleted

#

# @1 newline

#  orig:  gus = 89;     // @1 newline gus++;

#  new:   gus = 89;     //

#         gus++;

#

# @1 replace

#  orig:  gus = 89;     // @1 replace gus = 90;

#  new:   gus = 90;

#

# The only other tag supported is @1 breakpoint.  The setbkpts function

# sets bkpts at all lines that contain this string.

# 

# Currently, all these tags are start with @1.  It is envisioned that this script

# could be ehanced to allow multiple cycles of redefines by allowing

# @2, @3, ... tags.  IE, processing the @i tags in the ith version of

# the file will produce the i+1th version of the file.

# 

# There are problem with jtreg leaving behind orphan java and jdb processes

# when this script is run.  Sometimes, on some platforms, it just doesn't

# get them all killed properly.

# The solution is to put a magic word in the cmd lines of background java

# and jdb processes this script launches.  We can then do the right kind

# of ps cmds to find all these processes and kill them.  We do this by

# trapping the completion of this script.

#

# An associated problem is that our trap handler (cleanup) doesn't

# always get called when jtreg terminates a test.  This can leave tests

# hanging but following tests should run ok because each test uses

# unique names for the port and temp files (based on the PID returned

# by $$).

#

# mks 6.2a on win 98 presents two problems:

#   $! returns the PID as a negative number whereas ps returns

#      it in the form 0xFFF....  This means our trick of 

#      of using $! to get the PIDs of the jdb and debuggee processes

#      doesn't work.  This will cause some error cases to fail

#      with a jtreg timeout instead of failing more gracefully.

#

#   There is no form of the ps command that will show the whole

#   cmd line.  Thus, the magic keyword trick doesn't work.  We

#   resort to just killing java.exe and jdb.exes

#

# pid usage:

#   debuggeepid: used in jdb process to detect if debuggee has died.

#                - waitForDebuggeeMsg: fail if debuggee is gone

#

#   jdbpid:   dofail: used to detect if in main process or jdb process

#             waitforfinish: quit if the jdb process is gone

#killcmd=/bin/kill

killcmd=kill

# This can be increased if timing seems to be an issue.

sleep_seconds=1

echo "ShellScaffold.sh: Version" >& 2

topPid=$$

# Be careful to echo to >& in these general functions.

# If they are called from the functions that are sending

# cmds to jdb, then stdout is redirected to jdb.

cleanup()

{

    if [ -r "$failFile" ] ; then

        ls -l "$failFile" >&2

        echo "<cleanup:_begin_failFile_contents>" >&2

        cat "$failFile" >&2

        echo "<cleanup:_end_failFile_contents>" >&2

    fi

    # Kill all processes that have our special

    # keyword in their cmd line.

    killOrphans cleanup $jdbKeyword

    killOrphans cleanup $debuggeeKeyword

}

# Kill all processes with $2 in their cmd lines

# Print a msg about this using $1 as the prefix

killOrphans()

{

    str=$2

    if [ -z "$isCygwin" ] ; then

        toBeKilled=`$psCmd | $grep -v grep | $grep -i $str | awk '{print $1}' | tr '\n\r' '  '`

    else

        # The cygwin ps command doesn't show the options passed to a cmd.

        # We will use jps to get the win PID of the command, and

        # then use ps to find the cygwin pid to be killed.

        # The form of a ps output line is

        # ^   ddddd    dddd    dddd    dddd.*

        # where the 4th digits are the win pid and the first 

        # are the cygwin pid.

        if [ -r "$jdk/bin/$jstack" ] ; then

            winPid=`$jdk/bin/jps -v | $grep -i $str | sed -e 's@ .*@@'`

            if [ ! -z "$winPid" ] ; then

                # Here is a way to kill using a win cmd and the win PID.

                #echo "$1: taskkill /F $winPid"  >& 2

                #taskkill /F /PID $winPid

                toBeKilled=`$psCmd | $grep -v grep | \

                            $grep '^ +[0-9]+ +[0-9]+ +[0-9]+ +'"$winPid" |\

                            awk '{print $1}' | tr '\n\r' '  '`

            fi

        else

            # Well, too bad - we can't find what to kill.  

            toBeKilled=

        fi

    fi

    if [ ! -z "$toBeKilled" ] ; then

        echo "$1: kill -9 $toBeKilled"  >& 2

        kill -9 $toBeKilled

    fi

}    

findPid()

{

    # Return 0 if $1 is the pid of a running process.

    if [ -z "$isWin98" ] ; then

        if [ "$osname" = SunOS ] ; then

            # Solaris and OpenSolaris use pgrep and not ps in psCmd

            findPidCmd="$psCmd"

        else

            #   Never use plain 'ps', which requires a "controlling terminal"

            #     and will fail  with a "ps: no controlling terminal" error.

            #     Running under 'rsh' will cause this ps error.

            # cygwin ps puts an I in column 1 for some reason.

            findPidCmd="$psCmd -e"

        fi

	$findPidCmd | $grep '^I* *'"$1 " > $devnull 2>&1

        return $?

    fi

    # mks 6.2a on win98 has $! getting a negative

    # number and in ps, it shows up as 0x...

    # Thus, we can't search in ps output for 

    # PIDs gotten via $!

    # We don't know if it is running or not - assume it is.

    # We don't really care about win98 anymore.

    return 0

}

setup()

{

    failed=

    # This is used to tag each java and jdb cmd we issue so

    # we can kill them at the end of the run.

    orphanKeyword=HANGINGJAVA-$$

    debuggeeKeyword=${orphanKeyword}_DEB

    jdbKeyword=${orphanKeyword}_JDB

    baseArgs=-D${debuggeeKeyword}

    if [ -z "$TESTCLASSES" ] ; then

        echo "--Warning:  TESTCLASSES is not defined; using TESTCLASSES=."

        echo "  You should run: "

        echo "    runregress $0 -no"

        echo "  or"

        echo "    (setenv TESTCLASSES .; $0 $*)"

        TESTCLASSES=.

    fi

    if [ ! -z "$TESTJAVA" ] ; then

        jdk="$TESTJAVA"

    else

        echo "--Error: TESTJAVA must be defined as the pathname of a jdk to test."

        exit 1

    fi

    ulimitCmd=

    osname=`uname -s`

    isWin98=

    isCygwin=

    case "$osname" in

       Windows* | CYGWIN*)	   

	 if [ "$osname" = Windows_98 -o "$osname" = Windows_ME ]; then

             isWin98=1

             debuggeeKeyword='we_cant_kill_debuggees_on_win98'

             jdbKeyword='jdb\.exe'

	 fi

         case "$osname" in

           CYGWIN*)

             isCygwin=1

             ;;

         esac

         if [ -r $jdk/bin/dt_shmem.dll -o -r $jdk/jre/bin/dt_shmem.dll ] ; then

            transport=dt_shmem

            address=kkkk.$$

         else

            transport=dt_socket

            address=

         fi

         devnull=NUL

         baseArgs="$baseArgs -XX:-ShowMessageBoxOnError"

         # jtreg puts \\s in TESTCLASSES and some uses, eg. echo

         # treat them as control chars on mks (eg \t is tab)

         # Oops; windows mks really seems to want this cat line

         # to start in column 1

         if [ -w "$SystemRoot" ] ; then

            tmpFile=$SystemRoot/tmp.$$

         elif [ -w "$SYSTEMROOT" ] ; then

            tmpFile=$SYSTEMROOT/tmp.$$

         else

            tmpFile=tmp.$$

         fi

cat <<EOF >$tmpFile

$TESTCLASSES

EOF

         TESTCLASSES=`cat $tmpFile | sed -e 's@\\\\@/@g'`

         rm -f $tmpFile

         # on mks

         grep=egrep

         psCmd=ps

         jstack=jstack.exe

         ;;

       SunOS | Linux)

         transport=dt_socket

         address=

         devnull=/dev/null

         grep=egrep

         jstack=jstack

         # On linux, core files take a long time, and can leave

         # zombie processes

         if [ "$osname" = SunOS ] ; then

             # Experiments show Solaris '/usr/ucb/ps -axwww' and

             # '/usr/bin/pgrep -f -l' provide the same small amount of the

             # argv string (PRARGSZ=80 in /usr/include/sys/procfs.h)

             #  1) This seems to have been working OK in ShellScaffold.

             #  2) OpenSolaris does not provide /usr/ucb/ps, so use pgrep

             #     instead

             # The alternative would be to use /usr/bin/pargs [pid] to get

             # all the args for a process, splice them back into one

             # long string, then grep.

             UU=`/usr/xpg4/bin/id -u -n`

             psCmd="pgrep -f -l -U $UU"

         else

             ulimit -c 0

             # See bug 6238593.

             psCmd="ps axwww"

         fi

         ;;

       *)

         echo "--Error:  Unknown result from 'uname -s':  $osname"

         exit 1

         ;;

    esac

    tmpFileDir=$TESTCLASSES/aa$$

    TESTCLASSES=$tmpFileDir

    mkdir -p $tmpFileDir

    # This must not contain 'jdb' or it shows up

    # in grep of ps output for some platforms

    jdbOutFile=$tmpFileDir/jxdbOutput.txt

    rm -f $jdbOutFile

    touch $jdbOutFile

    debuggeeOutFile=$tmpFileDir/debuggeeOutput.txt

    failFile=$tmpFileDir/testFailed

    debuggeepidFile=$tmpFileDir/debuggeepid

    rm -f $failFile $debuggeepidFile

    if [ -f "$failFile" ]; then

        echo "ERROR: unable to delete existing failFile:" >&2

        ls -l "$failFile" >&2

    fi

    if [ -z "$pkg" ] ; then

        pkgSlash=

        pkgDot=

        redefineSubdir=.

    else

        pkgSlash=$pkg/

        pkgDot=$pkg.

        redefineSubdir=$pkgSlash

    fi

    if [ -z "$classname" ] ; then

        classname=shtest

    fi

    if [ -z "$java" ] ; then

        java=java

    fi

    if [ -z "$jdb" ] ; then

        jdb=$jdk/bin/jdb

    fi

####################################################3

####################################################3

####################################################3

####################################################3

#  sol:  this gets all processes killed but 

#        no jstack

#  linux same as above

#  win mks:  No dice; processes still running

    trap "cleanup" 0 1 2 3 4 6 9 10 15

    jdbOptions="$jdbOptions -J-D${jdbKeyword}"

}

docompile()

{

    if [ "$compile" = 0 ] ; then

        return

    fi

    saveDir=`pwd`

    cd $tmpFileDir

    rm -f *.java

    createJavaFile $classname

    # Compile two versions of the file, the original and with the

    # indicated lines modified.

    cp $classname.java.1 $classname.java

    echo "--Compiling first version of `pwd`/$classname.java with options: $compileOptions"

    # Result is in $pkgSlash$classname.class

    if [ -z "$javacCmd" ] ; then

        javacCmd=$jdk/bin/javac

    fi

    echo "compiling " `ls *.java`

    $javacCmd $compileOptions -d . *.java

    if [ $? != 0 ] ; then

       dofail "First compile failed"

    fi

    if [ -r vers1 ] ; then

        rm -rf vers1

    fi

    mkdir -p vers1

    mv *.class vers1

    if [ ! -z "$compileOptions2" ] ; then

        if [ "$compileOptions2" = none ] ; then

            compileOptions=

        else

            compileOptions=$compileOptions2

        fi

    fi

    while [ 1 = 1 ] ; do

        # Not really a loop; just a way to avoid goto

        # by using breaks

        sed -e '/@1 *delete/ d' \

            -e 's! *// *@1 *uncomment!     !' \

            -e 's!\(.*@1 *commentout\)!//\1!' \

            -e 's/@1 *newline/\

                 /' \

            -e 's/.*@1 *replace//' \

            $classname.java.1  >$classname.java

        cmp -s $classname.java.1 $classname.java

        if [ $? = 0 ] ; then

            break

        fi

        echo 

        echo "--Compiling second version of `pwd`/$classname.java with $compileOptions"

        $javacCmd $compileOptions -d . $classname.java

        if [ $? != 0 ] ; then

            dofail "Second compile failed"

        fi

        if [ -r vers2 ] ; then

            rm -rf vers2

        fi

        mkdir -p vers2

        mv *.class vers2

        mv $classname.java $classname.java.2

        cp $classname.java.1 $classname.java

        ###### Do the same for @2, and @3 allowing 3 redefines to occur.

        ###### If I had more time to write sed cmds, I would do

        ###### this in a loop.  But, I don't think we will ever need

        ###### more than 3 redefines.

        sed -e '/@2 *delete/ d' \

            -e 's! *// *@2 *uncomment!     !' \

            -e 's!\(.*@2 *commentout\)!//\1!' \

            -e 's/@2 *newline/\

                 /' \

            -e 's/.*@2 *replace//' \

            $classname.java.2 >$classname.java

        cmp -s $classname.java.2 $classname.java

        if [ $? = 0 ] ; then

            break

        fi

        echo 

        echo "--Compiling third version of `pwd`/$classname.java with $compileOptions"

        $javacCmd $compileOptions -d . $classname.java

        if [ $? != 0 ] ; then

            dofail "Third compile failed"

        fi

        if [ -r vers3 ] ; then

            rm -rf vers3

        fi

        mkdir -p vers3

        mv *.class vers3

        mv $classname.java $classname.java.3

        cp $classname.java.1 $classname.java

        ########

        sed -e '/@3 *delete/ d' \

            -e 's! *// *@3 *uncomment!     !' \

            -e 's!\(.*@3 *commentout\)!//\1!' \

            -e 's/@3 *newline/\

                    /' \

            -e 's/.*@3 *replace//' \

            $classname.java.3 >$classname.java

        cmp -s $classname.java.3 $classname.java

        if [ $? = 0 ] ; then

            break

        fi

        echo 

        echo "--Compiling fourth version of `pwd`/$classname.java with $compileOptions"

        $javacCmd $compileOptions -d . $classname.java

        if [ $? != 0 ] ; then

            dofail "fourth compile failed"

        fi

        if [ -r vers4 ] ; then

            rm -rf vers4

        fi

        mkdir -p vers4

        mv *.class vers4

        mv $classname.java $classname.java.4

        cp $classname.java.1 $classname.java

        break

        fgrep @4 $classname.java

        if [ $? = 0 ] ; then

            echo "--Error: @4 and above are not yet allowed"

            exit 1

        fi

    done

    cp vers1/* $redefineSubdir

    cd $saveDir

}

# Send a cmd to jdb and wait for the jdb prompt to appear.

# We don't want to allow > as a prompt because if the debuggee

# runs for awhile after a command, jdb will show this prompt

# but is not really ready to accept another command for the

# debuggee - ie, a cont in this state will be ignored.

# If it ever becomes necessary to send a jdb command before

# a  main[10] form of prompt appears, then this

# code will have to be modified.

cmd() 

{

    if [ $1 = quit -o -r "$failFile" ] ; then