|
(→Dump Table)
|
(Reverting)
|
| Line 1: | |||
| = *nix = | = *nix = | ||
| This section lists methods to obtain dumps on *nix-based platforms | This section lists methods to obtain dumps on *nix-based platforms | ||
| Line 38: | |||
| <th>Version</th> | <th>Version</th> | ||
| </tr> | </tr> | ||
| - | <tr><td align=center rowspan=4>Windows</td><td align=center rowspan=2>'''jstack''' ''(Thread Dump)''</td><td><font face=monospace>-l process-id#</font></td><td>Prints long listing information (locks, synchronizers, etc.) on a specified process ID#</td><td align=center rowspan=3>6, 7</td></tr> | + | <tr><td align=center rowspan=7>*nix</td><td align=center rowspan=1>'''jstack''' ''(Thread Dump)''</td><td><font face=monospace>-m process-id#</font></td><td>Prints mixed threads (Java & C++) on a specified process ID#</td><td align=center rowspan=4>5</td></tr> |
| + | <tr><td align=center rowspan=3>'''jmap''' ''(Heap Dump)''</td><td><font face=monospace>process-id#</font></td><td>Performs shared object mappings on the specified process ID#</td></tr> | ||
| + | <tr><td><font face=monospace>-heap process-id#</font></td><td>Performs a heap dump on the specified process ID#</td></tr> | ||
| + | <tr><td><font face=monospace>-histo process-id#</font></td><td>Prints the histogram for the specified process ID#</td></tr> | ||
| + | <tr><td align=center rowspan=2>'''jstack''' ''(Thread Dump)''</td><td><font face=monospace>-l process-id#</font></td><td>Prints long listing information (locks, synchronizers, etc.) on a specified process ID#</td><td align=center rowspan=3>6, 7</td></tr> | ||
| <tr><td><font face=monospace>-l -F process-id#</font></td><td>Force a stack dump when ''jstack'' isn't responding</td></tr> | <tr><td><font face=monospace>-l -F process-id#</font></td><td>Force a stack dump when ''jstack'' isn't responding</td></tr> | ||
| <tr><td align=center rowspan=1>'''jmap''' ''(Heap Dump)''</td><td><font face=monospace>-dump:format=b,file=''filename'' process-id#</font></td><td>Dumps the memory map of the target process-ID# to an '''hprof file''' within the current directory (or specified directory if you expand upon ''filename'')</td></tr> | <tr><td align=center rowspan=1>'''jmap''' ''(Heap Dump)''</td><td><font face=monospace>-dump:format=b,file=''filename'' process-id#</font></td><td>Dumps the memory map of the target process-ID# to an '''hprof file''' within the current directory (or specified directory if you expand upon ''filename'')</td></tr> | ||
| Line 44: | |||
| - | * '''jmap''' - This command will then dump a summary of the current memory map to the console. While not as sophisticated as the later versions of java, it still provides some rudimentary functionality. | + | * '''jmap''' - This command will then dump a summary of the current memory map to the console. While not as sophisticated as the later versions of java, it still provides some rudimentary functionality. This command will then dump the memory map of the target process-id# to an hprof file within the current directory (or specified directory if you expand on 'filename'). |
| - | * '''jstack''' - This command will then take a thread dump of the java process specified and dump it to the console. It will only provide both Java & C/C++ threads during the trace. You may want to consider redirecting this output to a file with the ''>'' modifier. | + | * '''jstack''' - This command will then take a thread dump of the java process specified and dump it to the console. It will only provide both Java & C/C++ threads during the trace. You may want to consider redirecting this output to a file with the ''>'' modifier. This command will then take a thread dump of the java process specified and dump it to the console. You may want to consider redirecting this output to a file with the ''>'' modifier. |
| = Windows = | = Windows = | ||
| This section lists methods to obtain fresh dumps on Windows-based platforms | This section lists methods to obtain fresh dumps on Windows-based platforms | ||
