Debugging the JVM Using dbx

10 More Discussions You Might Find Interesting

1. AIX

JVM Process Name

Hi - In AIX, how do I find the Java Virtual Machine Process Name running on a particular machine? I tried ps -ef | grep java but it does not return a process name. Please help.

2. UNIX for Dummies Questions & Answers

Hi all, I am starting a JVM in unix and when I use ps command on the pid of process starting JVM the output is something like this :- java -Xms32M -Xmx64M -Xmx128M I need to know what would be the value of Xmx in this case. And how to check that this value be picked while starting JVM...

3. Shell Programming and Scripting

What's my JVM bitness?

/apps/wls/bea10/jdk160_05/bin/java -d64 -version execve(): No such file or directory Error trying to exec /apps/wls/bea10/jdk160_05/bin/sparcv9/java. Check if file exists and permissions are set correctly. Failed to start a 64-bit JVM process from a 32-bit JVM. Verify all necessary J2SE...

4. AIX

Using dbx on AIX

Hi, We are porting a virtual machine application which emits native PowerPC instructions. The instructions are written to the data segment and are then executed, similar to the JIT / hot spot technology used in the Java VM. The problem is that the AIX debugger (dbx) will not show me stack...

5. Web Development

need help about jvm

hi all i want to install apache and tomcat in unix solaris 10 so i need to konw about heap and jvm memory architecture in jdk version 4 and 5 and 6 i want one help me i searched alot and i can't find something helo me

6. AIX

AIX JVM -32 or 64?

Friends, Can any one tell me what command should be used to check whether the JVM in AIX is 32 bit or 64 bit? Thanks, Govindh

7. AIX

JVM Setting

What should be the idle JVM setting for the LPAR having 16 GB of memory? Currently the JVM setting is set to -Xms1024M -Xmx10240M

8. UNIX for Advanced & Expert Users

need help on dbx commands?

Hi .. I have a core_dump in the server... AIX 5.3 . It was created by on proc executable called "ProcessIse" . from the log report i found the source file name "ProcessIseInterface.C" which created the core file. the core file name is : "core" under /iprs/bin directory. can you help me...

9. UNIX for Advanced & Expert Users

inside the JVM

Hi, does anyone know how to find out what's happening inside a JVM on a unix system? Like what processes are running, which ports, memory usage etc. I'm using AIX 5.2

10. UNIX for Dummies Questions & Answers

Instaling JVM

Hi Everyone I`ve just started with unix can some please help me execute this command via webmin on avirtual server or how do you execute such .bin file this is the error ./j2sdk-1_3_1_15-linux-i586.bin: not found > ls -l total 69124 -rw------- 1 root wheel 8380 May 15 18:01...

LEARN ABOUT OSF1

expand_dump

expand_dump(8)						      System Manager's Manual						    expand_dump(8)

NAME

       expand_dump - Produces a non-compressed kernel crash dump file

SYNOPSIS

       /usr/sbin/expand_dump input-file output-file

DESCRIPTION

       By  default, kernel crash dump files (vmzcore.#) are compressed during the crash dump.  Compressed core files can be examined by the latest
       versions of debugging tools that have been recompiled to support compressed crash dump files.  However, not  all  debugging  tools  may	be
       upgraded on a given system, or you may want to examine a crash dump from a remote system using an older version of a tool.  The expand_dump
       utility produces a file that can be read by tools that have not been upgraded to support compressed crash dump files.  This  non-compressed
       version can also be read by any upgraded tool.

       This  utility  can  only  be used with compressed crash dump files, and does not support any other form of compressed file.  You cannot use
       other decompression tools such as compress, gzip, or zip on a compressed crash dump file.

       Note that the non-compressed file will require significantly more disk storage space as it is possible to achieve compression ratios of	up
       to  60:1.  Check the available disk space before running expand_dump and estimate the size of the non-compressed file as follows: Run tests
       by halting your system and forcing a crash as described in the Kernel Debugging manual.	Use an upgraded debugger to determine the value of
       the  variable  dumpsize.   Multiply this vale by the 8Kb page size to approximate the required disk space of the non-compressed crash-dump.
       Run expand_dump and pipe the output file to /dev/null, noting the size of the file that is printed when expand_dump completes its task.

RETURN VALUES

       Successful completion of the decompression.  The user did not supply the correct number of command line arguments.  The	input  file  could
       not  be	read.	The  input file is not a compressed dump, or is corrupted.  The output file could not be created or opened for writing and
       truncated.  There was some problem writing to the output file (probably a full disk).  The input file is not formated consistantly.  It	is
       probably corrupted.  The input file could not be correctly decompressed.  It is probably corrupted.

EXAMPLES

       expand_dump vmzcore.4 vmcore.4

SEE ALSO

       Commands: dbx(1), kdbx(8), ladebug(1), savecore(8)

       Kernel Debugging

       System Administration

																    expand_dump(8)

UNIX and Linux RSS News