|
(→Dump Table)
|
(→Dump Table)
|
| Line 77: | |||
| <th>Arguments</th> | <th>Arguments</th> | ||
| <th>Description</th> | <th>Description</th> | ||
| - | <th>Version</th> | + | <th>Java</th> |
| </tr> | </tr> | ||
| <tr><td align=center rowspan=4>Windows</td><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><td rowspan=4 align=center>6, 7</tr> | <tr><td align=center rowspan=4>Windows</td><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><td rowspan=4 align=center>6, 7</tr> | ||
| Line 83: | |||
| <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> | ||
| </table> | </table> | ||
| - | * '''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. | ||
| - | * '''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. | ||
| = Appendix A: References = | = Appendix A: References = | ||
