GETAPPCORE(8)
π¦ getappcore β the manual, but make it make sense π¦
okay so you're in the Support Utilities Manual bestie, section 8, and this whole page is about getappcore. it's the tool that scoops up your crashed app's whole situation and bundles it into one archive. let's go π
β¨ NAME β¨
getappcore β Get Application Core File. that's it, that's the vibe. it gets the core. π₯
π SYNOPSIS π
getappcore [OPTIONS] -j PID | /path/to/core/file
so basically: options, then either -j PID or a path to your core file. pick a lane, bestie π«Ά
π DESCRIPTION π
okay so here's what it actually does: it creates an archive containing an application core, and all files required to analyze it β including the binary which created the core, and all required shared libraries β¨. also, tucked in the archive is a logfile containing RPM version information for further investigation by SUSE π
and like β you must specify the filename or the journal PID of the application core you want to submit. no skipping that, it's giving required π
the core file must be provided uncompressed. yes, literally.
the PID can be determined by the command coredumpctl list. and here's the tea: since systemd creates compressed core files by default, you should almost always prefer -j <PID> nowadays. ngl, it's just easier. and you can safely omit the -b option then π
πΈ OPTIONS πΈ
-hβ the help screen. classic. iconic. your first stop π«-bpath β path to the binary which generated the application core file-rsrnum β SUSE Service Request number associated with this issue (drop your ticket number here, bestie π«)-jPID β specifies a coredump PID number from the journal to extract, instead of specifying a core file on the file system. this is the main character option fr π-uβ automatically uploads archive to the SUSE FTP server using HTTPS π-fβ automatically uploads archive to the SUSE FTP server using FTPES π-vβ enable verbose messages. for when you need the app to tell you everything π£οΈ
β EXAMPLES β
here's the part where it's literally copy-paste and go:
getappcore -j 1345
getappcore -ur 00123456 -j 2344
getappcore -ur 00123456 -b /bin/rpm /core.15832
first one: just grab PID 1345 from the journal. second: grab PID 2344 and attach SR number 00123456 and upload it. third: old-school style with the binary path -b /bin/rpm and a core file sitting right there at /core.15832. slay π
π AUTHORS π
- Jason Record
<jason.record@suse.com> - Mike Latimer
<mlatimer@suse.com>
give them their flowers, they built this π·
π COPYRIGHT π
k so the legal bit, but make it respectful:
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, see <http://www.gnu.org/licenses/>.
fr fr read the license, it's not that long, you got this π«Ά
and that's the whole page, bestie π§ this one's from supportutils, dated 10 Mar 2020 β shoutout to the GETAPPCORE(8) girlies, go get that core πβ¨π
π¦ where this page comes from
- opensuse-leap 16.0: supportutils 3.2.14.2-160000.1.1 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms