Stuff about core-dump reinstate-ment in the manual and release notes.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5193

diff --git a/NEWS b/NEWS
index 2aa6963c67166a306a958297d290bc51e8b69156..f7614806b073c50907b2b075cd90972d2d39a435 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -59,6 +59,13 @@ Other user-visible changes:
 - The XML output format has changed slightly.  See
   docs/internals/xml-output.txt.
 
+- Core dumping has been reinstated (it was disabled in 3.0.0 and 3.0.1).
+  If your program crashes while running under Valgrind, a core file with
+  the name "vgcore.<pid>" will be created (if your settings allow core
+  file creation).  Note that the floating point information is not all
+  there.  If Valgrind itself crashes, the OS will create a normal core
+  file.
+
 The following are some user-visible changes that occurred in earlier
 versions that may not have been announced, or were announced but not
 widely noticed.  So we're mentioning them now.

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index 83dbd9a1f8313864bc29631817091a3cf56e9e99..022f9afcb3a21c547d2e822719db65855c747897 100644 (file)
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -1479,10 +1479,14 @@ to use <computeroutput>--vex-iropt-precise-memory-exns=yes</computeroutput>.
 
 <para>If your program dies as a result of a fatal core-dumping signal,
 Valgrind will generate its own core file
-(<computeroutput>vgcore.pidNNNNN</computeroutput>) containing your program's
+(<computeroutput>vgcore.NNNNN</computeroutput>) containing your program's
 state.  You may use this core file for post-mortem debugging with gdb or
 similar.  (Note: it will not generate a core if your core dump size limit is
-0.)</para>
+0.)  At the time of writing the core dumps do not include all the floating
+point register information.</para>
+
+<para>If Valgrind itself crashes (hopefully not) the operating system
+will create a core dump in the usual way.</para>
 
 </sect1>