abrt-action-analyze-java(1) [centos man page]

ABRT-ACTION-ANALYZ(1)						    ABRT Manual 					     ABRT-ACTION-ANALYZ(1)

NAME

       abrt-action-analyze-java - Calculate and save UUID & DUPHASH and determine the level of usability for reporting of a Java stack trace.

SYNOPSIS

       abrt-action-analyze-java [-v] [-d DIR] [-o] [-f FILE]

DESCRIPTION

       The tool reads the file named backtrace from a problem data directory, processes it and generates a universally unique identifier (UUID).
       Then it saves this data as new element uuid. It also checks whether the stack trace contains a remote address in any of its frames and if
       so it creates not-reportable element whose contents explains why the stack trace should not be reported into a bug tracking system.

   Integration with ABRT events
       abrt-action-analyze-java can be used to generate the UUID & DUPHAS of a newly saved Java stack trace.

	   EVENT=post-create analyzer=Java   abrt-action-analyze-java

OPTIONS

       -d DIR
	   Path to a problem directory. The tool reads the backtrace from stdin when neither this option nor -f is provided.

       -f FILE
	   Path to a stack trace. The tool reads the backtrace from stdin when neither this option nor -d is provided.

       -o
	   Print the result to stdout.

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

AUTHORS

       o   ABRT team

abrt-java-connector						    01/19/2014						     ABRT-ACTION-ANALYZ(1)

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

NAME

       abrt-action-generate-core-backtrace - Generates coredump-level backtrace

SYNOPSIS

       abrt-action-generate-core-backtrace [-v] [-r] [-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.

       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.

       -r
	   Do not hash function fingerprints. Useful for debugging.

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

AUTHORS

       o   ABRT team

abrt 2.1.11							    06/18/2014						     ABRT-ACTION-GENERA(1)