abrt-action-generate-core-backtrace man page on Scientific

Man page or keyword search:  
man Server   26626 pages
apropos Keyword Search (all sections)
Output format
Scientific logo
[printable version]

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

NAME
       abrt-action-generate-core-backtrace - Generates coredump-level
       (debuginfo-free) backtrace

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

DESCRIPTION
       This tool uses coredump from the file coredump and binary at the path
       stored in file executable in the problem directory to generate
       coredump-level backtrace.

       Coredump-level backtrace resembles ordinary backtrace in that it
       contains information about call frames present on the stack at the time
       of the crash. However, it only contains information that can be
       obtained from the coredump without debugging symbols available - mainly
       relative addresses of the stored instruction pointers. Such backtrace
       can still be useful for reporting and reproducing the bug and does not
       require debugging information files to be installed. See FILE FORMAT
       for the description of the generated file.

       The result is saved in the problem directory in a file named
       core_backtrace.

   Integration with libreport events
       abrt-action-generate-core-backtrace can be used as an analyzer for
       application crashes which dump core.

       Example usage in report_event.conf:

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

OPTIONS
       -d DIR
	   Path to problem directory.

       -v
	   Be more verbose. Can be given multiple times.

FILE FORMAT
       The generated file is a text file containing one line for each stack
       frame of the thread that most likely caused the crash. The line has
       following format:

	   BUILD_ID OFFSET SYMBOL MODNAME FINGERPRINT

       Where:

       BUILD_ID
	   Build ID of the binary file the address is mapped to as a
	   hexadecimal string.

       OFFSET
	   Offset from the start of the executable section of aforementioned
	   file the stored instruction pointer points to. Number in
	   hexadecimal format.

       SYMBOL
	   Name of the function if it is present in the binary (which is often
	   the case for shared libraries).

       MODNAME
	   Name of the module. Contains name of a library or [exe] if it is
	   the executable.

       FINGERPRINT
	   Fingerprint of the function the instruction pointer points to. Not
	   yet implemented.

       Dash in place of any of the parts indicates that the part is unknown.

AUTHORS
       ยท   ABRT team

abrt 2.0.8			  11/21/2013		 ABRT-ACTION-GENERA(1)
[top]

List of man pages available for Scientific

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net