Date: Fri, 20 Apr 2001 11:40:54 +0200 (CEST) From: edwin@mavetju.org To: FreeBSD-gnats-submit@freebsd.org Subject: docs/26728: [patch] FreeBSD Developers' Handbook: dumping core Message-ID: <20010420094054.DACA5236@cgmd76206.chello.nl>
next in thread | raw e-mail | index | archive | help
>Number: 26728
>Category: docs
>Synopsis: [patch] FreeBSD Developers' Handbook: dumping core
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Fri Apr 20 02:50:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Edwin Groothuis
>Release: FreeBSD 4.2-RELEASE i386
>Organization:
-
>Environment:
$FreeBSD: doc/en_US.ISO_8859-1/books/developers-handbook/tools/chapter.sgml,v 1.3 2001/04/09 09:26:16 nik Exp $
>Description:
The FreeBSD Developers' Handbook talks about one way of dumping
core, but there are two more possible ways to do it.
>How-To-Repeat:
n/a
>Fix:
--- chapter.sgml.old Fri Apr 20 11:25:12 2001
+++ chapter.sgml Fri Apr 20 11:37:15 2001
@@ -978,6 +978,16 @@
infinite loop, for instance. If your program happens to
trap <symbol>SIGABRT</symbol>, there are several other
signals which have a similar effect.</para>
+
+ <para>If you want to create a core dump from inside
+ your program, you can call the abort() function. See
+ the man page of abort(3) about this.</para>
+
+ <para>If you want to create a core dump from outside
+ your program, but doesn't want it to end, you can
+ use the gcore program. See the man page of gcore(1)
+ about this.</para>
+
</answer>
</qandaentry>
</qandaset>
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010420094054.DACA5236>