Query: gcore
OS: freebsd
Section: 1
Links: freebsd man pages all man pages
Forums: unix linux community forum categories
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
GCORE(1) BSD General Commands Manual GCORE(1)NAMEgcore -- get core images of running processSYNOPSISgcore [-f] [-s] [-c core] [executable] pidDESCRIPTIONThe gcore utility creates a core image of the specified process, suitable for use with gdb(1). By default, the core is written to the file ``core.<pid>''. The process identifier, pid, must be given on the command line. The following options are available: -c Write the core file to the specified file instead of ``core.<pid>''. -f Dumps all available segments, excluding only malformed and undumpable segments. Unlike the default invocation, this flag dumps map- pings of devices which may invalidate the state of device transactions or trigger other unexpected behavior. As a result, this flag should only be used when the behavior of the application and any devices it has mapped is fully understood and any side effects can be controlled or tolerated. -s Stop the process while gathering the core image, and resume it when done. This guarantees that the resulting core dump will be in a consistent state. The process is resumed even if it was already stopped. The same effect can be achieved manually with kill(1).FILEScore.<pid> the core imageHISTORYA gcore utility appeared in 4.2BSD.BUGSBecause of the ptrace(2) usage gcore may not work with processes which are actively being investigated with truss(1) or gdb(1). Addition- ally, interruptable sleeps may exit with EINTR. The gcore utility is not compatible with the original 4.2BSD version.BSDJuly 14, 2010 BSD
Related Man Pages |
---|
gcore(1) - mojave |
gcore(1) - debian |
gcore(1) - osx |
gcore(1) - xfree86 |
gcore(1) - php |
Similar Topics in the Unix Linux Community |
---|
Multithreading in Pro*C |
core dump |
dbx for core dump |
Unable to catch the output after core dump and bus error |
No core dump |