ABRT-ACTION-GENERA(1)

✨ ABRT-ACTION-GENERA(1) ✨ 🦋 ABRT Manual 🦋

💖 NAME

okay bestie, the name of this tool is abrt-action-generate-core-backtrace 🎀 and it's giving "generates coredump-level backtrace" 💅 (the full name is a whole mouthful but we love a long name, fr fr 😭)

🌸 SYNOPSIS

abrt-action-generate-core-backtrace [-v] [-r] [-d DIR]

🧚 DESCRIPTION

okay so this tool grabs the coredump from the file coredump and the binary at the path stored in the file executable inside the problem directory 🫶 and then it cooks up a coredump-level backtrace for you ✨

a coredump-level backtrace is lowkey like an ordinary backtrace, because it still holds info about the call frames that were sitting on the stack when the crash happened 💀 but here's the twist: it only has what you can pull straight out of the coredump without debugging symbols. so mainly you get the relative addresses of the stored instruction pointers 🙈 it's still super useful for reporting and reproducing the bug, and the best part is you don't need debugging information files installed 😭🔥

the result gets saved in the problem directory in a file called core_backtrace 🍓

🦋 Integration with libreport events

bestie, abrt-action-generate-core-backtrace can be used as an analyzer for application crashes that dump core 👑

here's an example of how to use it in report_event.conf:

EVENT=analyze analyzer=CCpp
        abrt-action-generate-core-backtrace

💜 OPTIONS

• -d DIR — point it at the path to the problem directory 📂
• -r — this one says do not hash the function fingerprints 🙅‍♀️ it's useful for debugging 🔍
• -v — be more verbose 📣 you can give it multiple times if you're feeling extra 💅

🎀 AUTHORS

• ABRT team 🌈

---

ok that's the whole tea, bestie 💖 stay curious, stay caffeinated, and happy debugging ✨ (source: abrt 2.17.9, dated 08/03/2026 🌸)