VirtualBox

Changes between Version 43 and Version 44 of Core_dump


Ignore:
Timestamp:
Mar 21, 2013 2:12:29 PM (12 years ago)
Author:
Michael Thayer
Comment:

Core dumps on Ubuntu need suid_dumpable to be enabled too.

Legend:

Unmodified
Added
Removed
Modified
  • Core_dump

    v43 v44  
    55= How to create a core dump on Linux =
    66
    7 The procedure for 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).
     7!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):
     8{{{
     9$ echo -n 1 | sudo tee /proc/sys/fs/suid_dumpable
     10}}}
     11The 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).
    812
    913== To create a core dump on an Ubuntu system ==
     
    1721
    1822== To create a core dump on non-Ubuntu systems ==
     23
    1924start !VirtualBox from a command line (e.g. xterm):
    2025{{{
    2126$ ulimit -c unlimited
    22 $ sudo su
    23 # echo -n 1 > /proc/sys/kernel/core_uses_pid
    24 # echo -n 1 > /proc/sys/fs/suid_dumpable
    25 # exit
     27$ echo -n 1 | sudo tee /proc/sys/fs/suid_dumpable
    2628$ VirtualBox
    2729}}}
    28 or better start the VM directly:
     30or if possible start the virtual machine directly:
    2931{{{
    3032$ ulimit -c unlimited
    31 $ sudo su
    32 # echo -n 1 > /proc/sys/kernel/core_uses_pid
    33 # echo -n 1 > /proc/sys/fs/suid_dumpable
    34 # exit
     33$ echo -n 1 | sudo tee /proc/sys/kernel/core_uses_pid
    3534$ /usr/lib/virtualbox/VirtualBox -startvm VM_NAME
    3635}}}
    3736Ensure that '''no''' startup script (`~/.bashrc`, `~/.bash_profile`, `~/.profile`) contains an instruction like `ulimit -c 0` as the limit cannot be increased once it was set to zero.
    38 
    39 Starting with version 2.0.0, the !VirtualBox processes are started `suid root`, that is, with permissions to do things that "normal" applications cannot. This is the reason for the
    40 {{{
    41 $ sudo su
    42 $ echo -n 1 > /proc/sys/fs/suid_dumpable
    43 $ exit
    44 }}}
    45 before starting the VM/GUI (note that `sudo echo` will not do what we want here).
    4637
    4738When !VirtualBox or one of its processes crashes, a file core.<pid> is created in the current directory. Be aware that core dumps can be very huge. Please compress the file before submitting it to a bug report. Or better don't attach the file to a report. Note that this core dump can contain a memory dump of your guest which can include sensitive information. Send it to frank _dot_ mehnert _at_ oracle _dot_ com if the compressed file is smaller than 5MB. Upload it to ftp.oracle.com:/appsdev/incoming and contact me directly otherwise to tell me the file name of the uploaded core dump.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette