From: Nicholas Nethercote Date: Fri, 18 Nov 2005 17:36:01 +0000 (+0000) Subject: Stuff about core-dump reinstate-ment in the manual and release notes. X-Git-Tag: svn/VALGRIND_3_1_0~39 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=aba486d88063baf0683198cf216159ad54a7bcd3;p=thirdparty%2Fvalgrind.git 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 2aa6963c67..f7614806b0 100644 --- 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." 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 83dbd9a1f8..022f9afcb3 100644 --- a/docs/xml/manual-core.xml +++ b/docs/xml/manual-core.xml @@ -1479,10 +1479,14 @@ to use --vex-iropt-precise-memory-exns=yes. If your program dies as a result of a fatal core-dumping signal, Valgrind will generate its own core file -(vgcore.pidNNNNN) containing your program's +(vgcore.NNNNN) 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.) +0.) At the time of writing the core dumps do not include all the floating +point register information. + +If Valgrind itself crashes (hopefully not) the operating system +will create a core dump in the usual way.