When to attach

ngaix.gif (1051 bytes)ngwin.gif (1069 bytes)Restriction: Attaching to a running process is only supported on AIX and Windows.

ngjava.gif (225 bytes)You can attach the debugger to an already running program or a running Java Virtual Machine (JVM) where an error or failure has occurred.

There are two main reasons for attaching the debugger to a process:

ngwin.gif (1069 bytes) You can also use the debug on demand feature to invoke the debugger when an application running on your system throws an exception that is not handled. Debug on demand is not available when debugging interpreted Java programs.

ngaix.gif (1051 bytes) You can also use postmortem debugging to debug a core file containing information on the state of an application when it trapped. Postmortem debugging is available when debugging locally only. Postmortem debugging is not available when debugging interpreted Java programs.

ngrelt.gif (466 bytes)
Attaching to a local running process
Attaching to a remote running process
ngjava.gif (225 bytes)Attaching to a running Java Virtual Machine
ngwin.gif (1069 bytes)Enabling and disabling debug on demand