Linux command
abrt-action-generate-backtrace 命令
文本
复制后可按需替换文件名、目录或参数。
常用示例
Generate backtrace
abrt-action-generate-backtrace -d [/var/spool/abrt/ccpp-2024-01-15]
Generate backtrace
abrt-action-generate-backtrace -v -d [/var/spool/abrt/ccpp-2024-01-15]
Generate backtrace
abrt-action-generate-backtrace -d [problem_dir] -i [/usr/lib/debug:/opt/debug]
Generate backtrace
abrt-action-generate-backtrace -d [problem_dir] -t [300]
说明
abrt-action-generate-backtrace is part of the ABRT (Automatic Bug Reporting Tool) suite. It analyzes a coredump file and generates a human-readable backtrace showing the state of an application at the moment it crashed. The tool runs gdb on a file named "coredump" in the specified problem directory. GDB generates the backtrace and other diagnostic information, which is then saved as a new element named "backtrace" in the problem directory. This backtrace can be used for debugging, bug reporting, or crash analysis. For best results, the corresponding debuginfo packages should be installed for the crashed application and its libraries. Without debugging symbols, the backtrace will contain only memory addresses rather than function names and line numbers. The tool integrates with libreport events and is typically invoked automatically by ABRT when analyzing C/C++ application crashes.
参数
- -d _DIR_
- Path to the problem directory containing the coredump file
- -v
- Be more verbose; can be specified multiple times for increased verbosity
- -i _DIR1:DIR2..._
- Additional debuginfo directories to search for debugging symbols
- -t _NUM_
- Kill gdb if it runs for more than NUM seconds (timeout)
FAQ
What is the abrt-action-generate-backtrace command used for?
abrt-action-generate-backtrace is part of the ABRT (Automatic Bug Reporting Tool) suite. It analyzes a coredump file and generates a human-readable backtrace showing the state of an application at the moment it crashed. The tool runs gdb on a file named "coredump" in the specified problem directory. GDB generates the backtrace and other diagnostic information, which is then saved as a new element named "backtrace" in the problem directory. This backtrace can be used for debugging, bug reporting, or crash analysis. For best results, the corresponding debuginfo packages should be installed for the crashed application and its libraries. Without debugging symbols, the backtrace will contain only memory addresses rather than function names and line numbers. The tool integrates with libreport events and is typically invoked automatically by ABRT when analyzing C/C++ application crashes.
How do I run a basic abrt-action-generate-backtrace example?
Run `abrt-action-generate-backtrace -d [/var/spool/abrt/ccpp-2024-01-15]` in a terminal, then adjust file names, paths, flags, or remote targets for your system.
What does -d _DIR_ do in abrt-action-generate-backtrace?
Path to the problem directory containing the coredump file