2006-08-15 17:59:38 +02:00
|
|
|
.TH DUMPCORE 1
|
|
|
|
|
.SH NAME
|
|
|
|
|
dumpcore \- generate core file of running process
|
|
|
|
|
.SH SYNOPSIS
|
2009-12-29 22:34:06 +01:00
|
|
|
dumpcore \fIpid\fR
|
2006-08-15 17:59:38 +02:00
|
|
|
.br
|
|
|
|
|
.de FL
|
|
|
|
|
.TP
|
|
|
|
|
\\fB\\$1\\fR
|
|
|
|
|
\\$2
|
|
|
|
|
..
|
|
|
|
|
.de EX
|
|
|
|
|
.TP 20
|
|
|
|
|
\\fB\\$1\\fR
|
|
|
|
|
# \\$2
|
|
|
|
|
..
|
|
|
|
|
.SH DESCRIPTION
|
2009-12-29 22:34:06 +01:00
|
|
|
The \fBdumpcore\fR utility generates a core file for a running process, based
|
|
|
|
|
on that process's process ID (\fIpid\fP). The resulting core file will be
|
|
|
|
|
stored under the name "core" in the current working directory. Any previous
|
|
|
|
|
file with that name will be overwritten.
|
|
|
|
|
.PP
|
|
|
|
|
The resulting core file can be used with for example
|
|
|
|
|
.BR mdb (1).
|
2006-08-15 17:59:38 +02:00
|
|
|
.SH BUGS
|
2009-12-29 22:34:06 +01:00
|
|
|
The process of generating the core file is currently very rudimentary, and
|
|
|
|
|
the generated core file does not contain for example memory mapped areas.
|
2006-08-15 17:59:38 +02:00
|
|
|
.SH "SEE ALSO"
|
2009-12-29 22:34:06 +01:00
|
|
|
.BR mdb (1).
|
