Changes between Version 47 and Version 48 of Core_dump

Timestamp:

Sep 29, 2014 6:48:40 AM (10 years ago)

Author:

Michael Thayer

Comment:

--

Core_dump

@@ -3 +3 @@
 A core dump is a technical term for a file containing detailed information about the state of an application at a given time, in a form which developers can make use of.  They are particularly helpful for tracking down the reasons for application crashes, which is why many systems can be told to create one automatically when an application crash occurs.
 
-= How to create a core dump on Linux =
+= How to create a core dump on Linux = #Linux
 
 !VirtualBox is (as of version 2.0.0) a system application which can be started from a user account without special privileges - a so-called "setuid" application.  As core dumps are usually not allowed for these sensitive applications you have to explicitly allow them after starting your computer but before the crash which you want a core dump from.  This can be done by typing the following command at the command line (your user account must be allowed to use the "sudo" command):
@@ -11 +11 @@
 The procedure for actually creating a core dump is similar on most Linux systems, but on Ubuntu it is slightly different due to the Ubuntu crash reporting tool (Apport).
 
-== To create a core dump on an Ubuntu system ==
+== To create a core dump on an Ubuntu system == #Ubuntu
 
 create a file called ".config/apport/settings" in your home directory with the contents
@@ -20 +20 @@
 and run !VirtualBox.  Any crashes of !VirtualBox after you have created the file will cause a crash report to be created in /var/crash with a name like "_usr_lib_virtualbox_VirtualBox.1000.crash".  Do not accept the offer to "Send an error report to help fix this problem".  You can extract the core file using the "apport-unpack" tool, or if you are unsure you can just send us the full crash report file.  To stop crash files being created for non-system applications delete the file that you created again.
 
-== To create a core dump on non-Ubuntu systems ==
+== To create a core dump on non-Ubuntu systems == #OtherLinux
 
 start !VirtualBox from a command line (e.g. xterm):
@@ -44 +44 @@
 to be sure of the right one to send.
 
-= How to create dumps on Mac OS X =
+= How to create dumps on Mac OS X = #OSX
 To create a core dump on Mac OS X, start !VirtualBox from a command line:
 {{{
@@ -65 +65 @@
 The core files can be found in the /cores folder.
 
-= How to create dumps on Solaris =
+= How to create dumps on Solaris = #Solaris
 To create a core dump on Solaris, run the following command as root
 {{{
@@ -84 +84 @@
 }}}
 
-= Forcing !VirtualBox to terminate with a core dump =
+= Forcing !VirtualBox to terminate with a core dump = #Forcing
 Sometimes it is required to force a !VirtualBox process to terminate, for example, a VM hangs for some unknown reason. On Linux, this can be done as follows:
 {{{
@@ -127 +127 @@
 
   
-= Minidumps on Windows =
+= Minidumps on Windows = #WindowsMiniDumps
 Please visit this [http://support.microsoft.com/kb/315263 Microsoft site] for more details about minidumps[[BR]]
 Please visit the [http://blogs.technet.com/askperf/archive/2007/06/15/capturing-application-crash-dumps.aspx Microsoft Performance Team blog] for more details about Application crash dumps
 
-= User mode crash dumps on Windows Vista and Windows 7 =
+= User mode crash dumps on Windows Vista and Windows 7 = #WindowsUserMode
 The section '''To collect user-mode dumps''' of the [http://support.microsoft.com/kb/315263 Microsoft site] explains how to enable user mode dumps on Windows Vista and Windows 7[[BR]]
 More detailed information about collecting user-mode dumps is available on the [http://msdn.microsoft.com/en-us/library/bb787181(VS.85).aspx MSDN site]