- Timestamp:
- Sep 10, 2010 11:18:08 AM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_AdvancedTopics.xml
r32387 r32391 1355 1355 core dump directory.</para> 1356 1356 1357 <para>Next you need to specify when the VirtualBox CoreDumper should be 1358 triggered. You can replace the system core dumper, or ask it to setup it's 1359 core dumper for live, running processes without terminating the VM. This 1360 is done using the following commands:</para> 1357 <para>You must specify when the VirtualBox CoreDumper should be triggered. 1358 This is done using the following commands:</para> 1361 1359 1362 1360 <para><screen>VBoxManage setextradata "VM name" VBoxInternal2/CoreDumpReplaceSystemDump 1 … … 1366 1364 1367 1365 <para>Setting <computeroutput>CoreDumpReplaceSystemDump</computeroutput> 1368 overrides the host's core dumping mechanism and in the event of any crash 1369 only the VirtualBox CoreDumper would produced the core file.</para> 1366 sets up the VM to override the host's core dumping mechanism and in the 1367 event of any crash only the VirtualBox CoreDumper would produce the core 1368 file.</para> 1370 1369 1371 1370 <para>Setting <computeroutput>CoreDumpLive</computeroutput> sets up the VM 1372 1371 to produce cores whenever the VM receives a 1373 1372 <computeroutput>SIGUSR2</computeroutput> signal. After producing the core 1374 file, the VM will not be terminated and will continue to run. You can th us1375 take cores of the VM process anytimeusing:</para>1373 file, the VM will not be terminated and will continue to run. You can then 1374 take cores of the VM process using:</para> 1376 1375 1377 1376 <para><screen>kill -s SIGUSR2 <VM-process-id></screen></para>
Note:
See TracChangeset
for help on using the changeset viewer.