6 .Nd get core images of running processes
12 .Op Fl o Ar path | Fl c Ar pathformat
17 program creates a core file image of the process specified by
19 The resulting core file can be used with a debugger, e.g.
21 to examine the state of the process.
23 The following options are available:
26 Suspend the process while the core file is captured.
28 Report progress on the dump as it proceeds.
30 Limit the size of the core file to
35 The following options control the name of the core file:
38 Write the core file to
40 .It Fl c Ar pathformat
41 Write the core file to
45 string is treated as a pathname that may contain various special
46 characters which cause the interpolation of strings representing
47 specific attributes of the process into the name.
49 Each special character is introduced by the
51 character. The format characters and their meanings are:
54 The name of the program being dumped, as reported by
57 The uid of the process being dumped, converted to a string.
59 The pid of the process being dumped, converted to a string.
61 The time when the core file was taken, converted to ISO 8601 format.
63 Output a percent character.
67 The default file name used by
71 By default, the core file will be written to a directory whose
72 name is determined from the
74 MIB. This can be printed or modified using
77 The directory where the core file is to be written must be
78 accessible to the owner of the target process.
81 will not overwrite an existing file,
82 nor will it create missing directories in the path.
87 .Bl -tag -width "/cores/%N-%P-%T plus" -compact
88 .It Pa /cores/%N-%P-%T
89 default pathname for the corefile.
96 writes out as much data as it can up to the specified limit,
97 even if that results in an incomplete core image.
98 Such a partial core dump may confuse subsequent
99 programs that attempt to parse the contents of such files.