Normally, sudo disables core dumps while it is running. This

behavior can now be modified at run time with a line in sudo.conf
like "Set disable_coredumps false"

--HG--
branch : 1.8

diff --cc doc/sudo.cat
index 21031849387dfe710bd90c4dcf1e00dcdf5d78ed,038fb46d13905e659dd18e2fe1c9fb0c5d5c99f7..b28d97d82d5ef3eb5e1f7f038c1b034f6dcc3629
--- 1/doc/sudo.cat
--- 2/doc/sudo.cat
+++ b/doc/sudo.cat
@@@ -327,9 -405,7 +327,10 @@@ P\bPL\bLU\bUG\bGI\bIN\bNS\b
          #
          # Format:
          #   Plugin plugin_name plugin_path
 -        #   Path askpass path/to/askpass
 +        #   Path askpass /path/to/askpass
 +        #   Path noexec /path/to/noexec.so
 +        #   Debug sudo /var/log/sudo_debug all@warn
++        #   Set disable_coredump true
          #
          # The plugin_path is relative to /usr/local/libexec unless
          #   fully qualified.
@@@ -445,6 -474,6 +446,20 @@@ S\bSE\bEC\bCU\bUR\bRI\bIT\bTY\bY N\bNO\bOT\bTE\bES\b
         information, please see the PREVENTING SHELL ESCAPES section in
         _\bs_\bu_\bd_\bo_\be_\br_\bs(4).
  
++       To prevent the disclosure of potentially sensitive information, s\bsu\bud\bdo\bo
++       disables core dumps by default while it is executing (they are re-
++       enabled for the command that is run).  To aid in debugging s\bsu\bud\bdo\bo
++       crashes, you may wish to re-enable core dumps by setting
++       "disable_coredump" to false in the _\b/_\be_\bt_\bc_\b/_\bs_\bu_\bd_\bo_\b._\bc_\bo_\bn_\bf file.
++
++        Set disable_coredump false
++
++       Note that by default, most operating systems disable core dumps from
++       setuid programs, which includes s\bsu\bud\bdo\bo.  To actually get a s\bsu\bud\bdo\bo core file
++       you may need to enable core dumps for setuid processes.  On BSD and
++       Linux systems this is accomplished via the sysctl command, on Solaris
++       the coreadm command can be used.
++
  E\bEN\bNV\bVI\bIR\bRO\bON\bNM\bME\bEN\bNT\bT
         s\bsu\bud\bdo\bo utilizes the following environment variables.  The security policy
         has control over the content of the command's environment.
@@@ -582,4 -629,32 +597,4 @@@ D\bDI\bIS\bSC\bCL\bLA\bAI\bIM\bME\bER\b
  
  
  
- 1.8.4                          January  6, 2012                       SUDO(1m)
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -
 -1.8.0rc1                February 21, 2011                      10
 -
 -
++1.8.4                          February  3, 2012                      SUDO(1m)

diff --cc doc/sudo.man.in
index ee15f8f04705d077388b8ab7d32ae34f17181c90,55a16b47215b0fa30637f31acd286f7dfa12db46..bdd8da06ab1baf196fa7194d3ad66d68dab5427c
--- 1/doc/sudo.man.in
--- 2/doc/sudo.man.in
+++ b/doc/sudo.man.in
@@@ -149,7 -149,7 +149,7 @@@
  .\" ========================================================================
  .\"
  .IX Title "SUDO @mansectsu@"
- .TH SUDO @mansectsu@ "January  6, 2012" "1.8.4" "MAINTENANCE COMMANDS"
 -.TH SUDO @mansectsu@ "February 21, 2011" "1.8.0rc1" "MAINTENANCE COMMANDS"
++.TH SUDO @mansectsu@ "February  3, 2012" "1.8.4" "MAINTENANCE COMMANDS"
  .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
  .\" way too many mistakes in technical documents.
  .if n .ad l
@@@ -527,9 -532,7 +527,10 @@@ which corresponds to the following \fI@
  \& #
  \& # Format:
  \& #   Plugin plugin_name plugin_path
 -\& #   Path askpass path/to/askpass
 +\& #   Path askpass /path/to/askpass
 +\& #   Path noexec /path/to/noexec.so
 +\& #   Debug sudo /var/log/sudo_debug all@warn
++\& #   Set disable_coredump true
  \& #
  \& # The plugin_path is relative to @prefix@/libexec unless
  \& #   fully qualified.
@@@ -652,6 -590,6 +653,22 @@@ Because of this, care must be taken whe
  commands via \fBsudo\fR to verify that the command does not inadvertently
  give the user an effective root shell.  For more information, please
  see the \f(CW\*(C`PREVENTING SHELL ESCAPES\*(C'\fR section in \fIsudoers\fR\|(@mansectform@).
++.PP
++To prevent the disclosure of potentially sensitive information,
++\&\fBsudo\fR disables core dumps by default while it is executing (they
++are re-enabled for the command that is run).  To aid in debugging
++\&\fBsudo\fR crashes, you may wish to re-enable core dumps by setting
++\&\*(L"disable_coredump\*(R" to false in the \fI@sysconfdir@/sudo.conf\fR file.
++.PP
++.Vb 1
++\& Set disable_coredump false
++.Ve
++.PP
++Note that by default, most operating systems disable core dumps
++from setuid programs, which includes \fBsudo\fR.  To actually get a
++\&\fBsudo\fR core file you may need to enable core dumps for setuid
++processes.  On \s-1BSD\s0 and Linux systems this is accomplished via the
++sysctl command, on Solaris the coreadm command can be used.
  .SH "ENVIRONMENT"
  .IX Header "ENVIRONMENT"
  \&\fBsudo\fR utilizes the following environment variables.  The security