IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Overview of the available diagnostic tools

Scenarios in which dumps might not be produced

In certain scenarios, a dump is not produced when a crash occurs. This section gives reasons why a dump is not produced and suggests how you can obtain a system dump.

A crash can occur with no dump produced. An example scenario is one in which the crash occurs during the shut down of the Java™ runtime environment. The Java runtime environment might not have time to produce all the debug information. In this case, the console output shows the start of the dump information, but the Java runtime environment cannot write the information in a dump file. For example, the console might show the following output:

Unhandled exception
Type=Segmentation error vmState=0x00000000
J9Generic_Signal_Number=00000004 ExceptionCode=c0000005 ExceptionAddress=430514B
E ContextFlags=0001003f
Handler1=7FEE9C40 Handler2=7FEC98C0 InaccessibleAddress=00000000
EDI=000A7060 ESI=43159598 EAX=00000000 EBX=001925EC
ECX=00000001 EDX=4368FECC
EIP=430514BE ESP=4368FED4 EBP=4368FED8 EFLAGS=00010246
Module=failing_module.dll
Module_base_address=43050000 Offset_in_DLL=000014be
Target=2_40_20081203_026494_lHdSMr (Windows XP 5.1 build 2600 Service Pack 2)
CPU=x86 (2 logical CPUs) (0x7fe6b000 RAM)

A diagnostic dump is not produced for several possible reasons. A common reason is that the Java runtime process was stopped by a user, a script, or by the operating system. Another possible reason is that the crash occurred on a JVM process that was very close to shut down, resulting in a race condition between the JVM dump handler and the main thread exiting the process.

• Identifying if the race condition exists
  Enable trace points to check for situations in which no dump is produced after a crash.
• Obtaining system dumps in a race condition
  You might be able to obtain system dumps even when a race condition exists.
• Stack overflow conditions in Windows
  In certain conditions, a stack overflow might cause failures when producing dumps.
• Native memory exhaustion in Windows
  The operating system process running the JVM does not have enough memory to produce the dump.

Parent: Overview of the available diagnostic tools

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.