HP-UX

Originally Posted by hergp

Do you have adb on HP-UX? If so, you could try

Code:

adb programfile corefile
    $c
    $q

That should give you a stack backtrace (syntax from memory and from Solaris, hope I got it right and the syntax is the same).

Originally Posted by hergp

programfileis the filename or pathname of the program which generated the core file.

When you start adb, you find yourself in an interactive mode without any prompt

The first command, $c, prints the stack backtrace. The second command, $q, terminates adb and you'll find yourself at the shell prompt.

That is, if adb on HP-UX works the same, as on Solaris.

Originally Posted by hergp

You can produce an outputfile with:

Code:

adb programfile corefile <<EOF >>log
    $c
    $q
EOF

The file command tells you the program name, but not the path. You might get a clue when you look at the output from ps -ef | grep java when your Java program is running fine. Take into account, that java is a symbolic link in most installations.

bea 8422 8406 0 22:50:49 ? 72:31 /opt/app/d1grn1m1/app1/jdk150_07/bin/IA64N/java -server -Xms1024m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:NewSize=512m -XX:MaxNewSize=512m -XX:SurvivorRatio=8 -Xnoclassgc -XX:+DisableExplicitGC -verbose:gc -XX:+UseParNewGC -XX:+CMSParallelRemarkEnabled -XX:+UseConcMarkSweepGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -da -Dplatform.home=/opt/app/app1/bea/weblogic92 -Dwls.home=/opt/app/app1/bea/weblogic92/server -Dwli.home=/opt/app/app1/bea/weblogic92/integration -Dweblogic.management.discover=false -Dweblogic.management.server=servera:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/appl/bea/patch_weblogic922/profiles/default/sysext_manifest_classpath -Dxng.log.server=myserver -javaagent:/appl/introscope/wily/Agent.jar -Dcom.wily.introscope.agentProfile=/appl/introscope/Agentfiles/IntroscopeAgent.profile -Dintroscope.agent.agentName=myserver -Dwebl