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

Stack overflow conditions in Windows

In certain conditions, a stack overflow might cause failures when producing dumps.

Stack overflows on Windows are identified by a value of c00000fd for the ExceptionCode as shown in the following output:

Unhandled exception
Type=Unhandled trap vmState=0x00040000
J9Generic_Signal_Number=00000040 ExceptionCode=c00000fd ExceptionAddress=7F646CA7
 ContextFlags=0001003f
Handler1=7FEE9C60 Handler2=7FEC9770
EDI=23CB4DCC ESI=23CB4DCC EAX=3F286561 EBX=23CAFF30
ECX=23C09CE4 EDX=7F65ED78
EIP=7F646CA7 ESP=24033000 EBP=2403303C EFLAGS=00010202
Module=failing_module.dll
Module_base_address=7F640000 Offset_in_DLL=00006ca7
Target=2_40_20080926_023633_lHdSMr (Windows Server 2003 5.2 build 3790 
Service Pack 2)
CPU=x86 (2 logical CPUs) (0x3ff78000 RAM)

The size of the overflow affects whether the dump succeeds, partially succeeds, or fails. In addition, the console data might be truncated. If you see ExceptionCode=c00000fd, a stack overflow has occurred. You can use a Windows debugger such as WinDbg or Visual Studio or the Windows Task Manager to generate a system dump in these circumstances. You might need to use the -Xrs command-line option to force the operating system to stop the JVM. In this case, a Windows dialog box indicates when the crash occurs. For more information about how to generate a system dump, see Collecting system dumps on Windows when -Xrs is set.

Parent: Scenarios in which dumps might not be produced

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.