Commit | Line | Data |
---|---|---|
98473598 C |
1 | GCORE(1) BSD Reference Manual GCORE(1) |
2 | ||
3 | N\bNA\bAM\bME\bE | |
4 | g\bgc\bco\bor\bre\be - get core images of running process | |
5 | ||
6 | S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS | |
7 | g\bgc\bco\bor\bre\be [-\b-s\bs] [-\b-c\bc _\bc_\bo_\br_\be] _\be_\bx_\be_\bc _\bp_\bi_\bd | |
8 | ||
9 | D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN | |
10 | G\bGc\bco\bor\bre\be creates a core image of the specified process, suitable for use | |
11 | with gdb(1). By default, the core is written to the file ``_\bc_\bo_\br_\be_\b._\b<_\bp_\bi_\bd_\b>''. | |
12 | Both the executable image, _\be_\bx_\be_\bc, and the process identifier, _\bp_\bi_\bd, must be | |
13 | given on the command line. | |
14 | ||
15 | The options are: | |
16 | ||
17 | -\b-c\bc Write the core file to the specified file instead of | |
18 | ``_\bc_\bo_\br_\be_\b._\b<_\bp_\bi_\bd_\b>''. | |
19 | ||
20 | -\b-s\bs Stop the process while gathering the core image, and resume it | |
21 | when done. This guarantees that the resulting core dump will be | |
22 | in a consistent state. The process is resumed even if it was al- | |
23 | ready stopped. The same effect can be achieved manually with | |
24 | kill(1). | |
25 | ||
26 | F\bFI\bIL\bLE\bES\bS | |
27 | core.<pid> The core image. | |
28 | ||
29 | H\bHI\bIS\bST\bTO\bOR\bRY\bY | |
30 | G\bGc\bco\bor\bre\be appeared in 4.2BSD. | |
31 | ||
32 | B\bBU\bUG\bGS\bS | |
33 | Context switches or paging activity that occur while g\bgc\bco\bor\bre\be is running may | |
34 | cause the program to become confused. For best results, use -s to tem- | |
35 | porarily stop the target process. | |
36 | ||
37 | G\bGc\bco\bor\bre\be is not compatible with the original 4.2BSD version. In particular, | |
38 | 4.4BSD requires the _\be_\bx_\be_\bc argumemt. | |
39 | ||
40 | 4.2 Berkeley Distribution June 6, 1993 1 |