gcore(1)

gcore1

Generate a core file of a running program

Usage

gcore [{-v | --version}] [{-h | --help}] [-a] [-o prefix] [-d directory]

pid1 [pid2 ... pidN]

Overview

Generate core dumps of one or more running programs with process IDs pid1, pid2, etc. A core file produced by gcore is equivalent to one produced by the kernel when the process crashes (and when "ulimit -c" was used to set up an appropriate core dump limit). However, unlike after a crash, after gcore finishes its job the program remains running without any change.

Options

-a

Dump all memory mappings. The actual effect of this option depends on the Operating System. On GNU/Linux, it will disable "use-coredump-filter" and enable "dump-excluded-mappings".

-o prefix

The optional argument prefix specifies the prefix to be used when composing the file names of the core dumps. The file name is composed as prefix.pid, where pid is the process ID of the running program being analyzed by gcore. If not specified, prefix defaults to core.

-g gdb

Use gdb as the executable binary to invoke GDB for running the gcore command. This argument is optional, and defaults to invoking the GDB binary that is installed alongside gcore.

-d directory

Use directory as the data directory when invoking GDB for running the gcore command. This argument is optional.

--help
-h

List all options, with brief explanations.

--version
-v

Print version information and then exit.

Environment

Releases

10 releases since Debian 5.0 (Lenny); the text changed 2 times.

  1. 5.0–10
  2. 11–13
  3. Arch

--help since Arch Linux 2026-11-01; --version since Arch Linux 2026-11-01; -a since Debian 11 (Bullseye); -d since Arch Linux 2026-11-01; -g since Arch Linux 2026-11-01; -h since Arch Linux 2026-11-01; -v since Arch Linux 2026-11-01.

From gdb 18.1-1 in Arch Linux 2026-11-01. Parsed by carta from the page's man source.