GCORE(1)

📦
version 7.2.4 · 2 versions
, in arch rolling

🫶 GCORE(1) — the manual page, but make it make sense

okay so real talk, this is the GCORE(1) page from the GNU Development Tools crew, and it's genuinely one of the most useful little gremlins in your toolbox. Let me walk you through it, bestie. 💅

✨ NAME ✨

gcore — generate a core file of a running program 🎀

✨ SYNOPSIS ✨

gcore [-a] [-o prefix] [-d directory] pid1 [pid2...pidN]

✨ DESCRIPTION ✨

So here's the vibe: gcore generates core dumps of one or more running programs, using the process IDs pid1, pid2, etc. You heard me. One or more. It's giving multitasking icon. 👑

A core file produced by gcore is equivalent to the one the kernel produces when the process crashes — you know, the one you get when ulimit -c was used to set up an appropriate core dump limit. Same energy, same content. 🫶

But here's the part that absolutely ate: unlike after a crash, once gcore finishes its job, the program just… keeps running. Without any change. No drama, no casualties, no "oops I killed production." It's literally the polite version of a core dump. 😭✨

✨ OPTIONS ✨

  • -a — dump all memory mappings. Lowkey the actual effect of this option depends on the Operating System, so it's not universal, bestie. On GNU/Linux specifically, it will disable use-coredump-filter and enable dump-excluded-mappings. iykyk. 🌸
  • -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 you don't specify it, prefix defaults to gcore. Cute, right? Default slay. 🎀
  • -d directory — use directory as the data directory when invoking ROCGDB for running the gcore command. This argument is optional. ✨

✨ ENVIRONMENT ✨

Okay so bestie, I'm gonna be so fr with you: this section is literally empty in the original. Nothing listed. Nothing to report. The vibe check came back blank 💀 — but I promised to keep every section, so here it is in all its glorious emptiness. 🦋

✨ SEE ALSO ✨

The full documentation for ROCGDB is maintained as a Texinfo manual. So if the info and gdb programs and ROCGDB's Texinfo documentation are all properly installed at your site, then this command:

info gdb

should give you access to the complete manual. Iconic. 🔥

Also, this absolute classic: Using GDB: A Guide to the GNU Source-Level Debugger, by Richard M. Stallman and Roland H. Pesch, July 1991. Old money. Vintage. We respect it. 💜

Copyright © 1988-2024 Free Software Foundation, Inc. ⭐

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with the Invariant Sections being "Free Software" and "Free Software Needs Free Documentation", with the Front-Cover Texts being "A GNU Manual," and with the Back-Cover Texts as in (a) below.

(a) The FSF's Back-Cover Text is: "You are free to copy and modify this GNU Manual. Buying copies from GNU Press supports the FSF in developing GNU and promoting software freedom." 🫶

AMD ROCm software is made available by Advanced Micro Devices, Inc. under the open source license identified in the top-level directory for the library in the repository on @url{https://github.com/ROCm/,Github.com} (Portions of AMD ROCm software are licensed under MITx11 and UIL/NCSA. For more information on the license, review the license.txt in the top-level directory for the library on @url{https://github.com/ROCm/,Github.com}). The additional terms and conditions below apply to your use of AMD ROCm technical documentation. 📄

©2019-2024 Advanced Micro Devices, Inc. All rights reserved.

The information presented in this document is for informational purposes only and may contain technical inaccuracies, omissions, and typographical errors. The information contained herein is subject to change and may be rendered inaccurate for many reasons, including but not limited to product and roadmap changes, component and motherboard version changes, new model and/or product releases, product differences between differing manufacturers, software changes, BIOS flashes, firmware upgrades, or the like. Any computer system has risks of security vulnerabilities that cannot be completely prevented or mitigated. AMD assumes no obligation to update or otherwise correct or revise this information. However, AMD reserves the right to revise this information and to make changes from time to time to the content hereof without obligation of AMD to notify any person of such revisions or changes.

THIS INFORMATION IS PROVIDED "AS IS." AMD MAKES NO REPRESENTATIONS OR WARRANTIES WITH RESPECT TO THE CONTENTS HEREOF AND ASSUMES NO RESPONSIBILITY FOR ANY INACCURACIES, ERRORS, OR OMISSIONS THAT MAY APPEAR IN THIS INFORMATION. AMD SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AMD BE LIABLE TO ANY PERSON FOR ANY RELIANCE, DIRECT, INDIRECT, SPECIAL, OR OTHER CONSEQUENTIAL DAMAGES ARISING FROM THE USE OF ANY INFORMATION CONTAINED HEREIN, EVEN IF AMD IS EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

AMD, the AMD Arrow logo, AMD Instinct™, Radeon™, AMD ROCm™, and combinations thereof are trademarks of Advanced Micro Devices, Inc. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. PCIe® is a registered trademark of PCI-SIG Corporation. Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies. 💀

okay that's the whole page, no skips, no shortcuts, every crumb of legal text included because I love you and I want you to have the entire thing. 🧚

sign-off era: this little masterpiece is from gdb-16.3, dated 2026-05-31 — go forth and dump some cores, bestie, your processes will literally be fine 💖🍓🌸

📦 where this page comes from