1gcore(1)                         User Commands                        gcore(1)
2
3
4

NAME

6       gcore - get core images of running processes
7

SYNOPSIS

9       gcore [-pgF] [-o filename] [-c content] process-id...
10
11

DESCRIPTION

13       The  gcore  utility  creates a core image of each specified process. By
14       default, the name of the core image file for the process whose  process
15       ID is process-id is core.process-id.
16

OPTIONS

18       The following options are supported:
19
20       -c content     Produces  core  image  files with the specified content.
21                      The content description uses the same tokens as in core‐
22                      adm(1M).  The -c option does not apply to cores produced
23                      due to the -p or -g flags.
24
25
26       -F             Force. Grabs the target process even if another  process
27                      has control.
28
29
30       -g             Produces core image files in the global core file repos‐
31                      itory with the global content  as  configured  by  core‐
32                      adm(1M).  The  command  fails  if the user does not have
33                      permissions to the global core file repository.
34
35
36       -o filename    Substitutes filename in place of core as the first  part
37                      of  the  name of the core image files. filename can con‐
38                      tain the same tokens to be  expanded  as  the  paths  in
39                      coreadm(1M).
40
41
42       -p             Produces a core image file in the process-specific loca‐
43                      tion with the process-specific content for each  process
44                      as  configured  by coreadm(1M). The command fails if the
45                      user does not have permissions to the  per-process  core
46                      file repository.
47
48

OPERANDS

50       The following operand is supported:
51
52       process-id    process ID
53
54

USAGE

56       Caution  should  be exercised when using the -F flag. Imposing two con‐
57       trolling processes on one victim process can lead to chaos.  Safety  is
58       assured  only if the primary controlling process, typically a debugger,
59       has stopped the victim process and the primary controlling  process  is
60       doing  nothing  at  the moment of application of the proc tool in ques‐
61       tion.
62

EXIT STATUS

64       The following exit values are returned:
65
66       0           On success.
67
68
69       non-zero    On failure, such as non-existent process ID.
70
71

FILES

73       core.process-id    core images
74
75

ATTRIBUTES

77       See attributes(5) for descriptions of the following attributes:
78
79
80
81
82       ┌─────────────────────────────┬─────────────────────────────┐
83       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
84       ├─────────────────────────────┼─────────────────────────────┤
85       │Availability                 │SUNWtoo                      │
86       ├─────────────────────────────┼─────────────────────────────┤
87       │Interface Stability          │See below.                   │
88       └─────────────────────────────┴─────────────────────────────┘
89
90
91       The command syntax is Evolving. The Output Formats are Unstable.
92

SEE ALSO

94       kill(1), coreadm(1M), setrlimit(2), core(4), proc(4), attributes(5)
95

NOTES

97       gcore  is  unaffected  by  the  setrlimit(2)  system  call  using   the
98       RLIMIT_CORE value.
99
100
101
102SunOS 5.11                        19 Jun 2006                         gcore(1)
Impressum