From Fedora Project Wiki

No edit summary
No edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 2: Line 2:
|description=This test case tests [[Features/RetraceServer|Retrace Server]]'s integration into [[Features/ABRT|ABRT]] GUI.
|description=This test case tests [[Features/RetraceServer|Retrace Server]]'s integration into [[Features/ABRT|ABRT]] GUI.
|setup=
|setup=
# Install retrace client - su -c 'yum install abrt-retrace-client'
# Ensure you have the plugin installed with the following command:
#* {{command|su -c 'yum install abrt-retrace-client'}}
# Make sure you have ABRT crashes caught by CCpp (crashes in C and C++ applications) that need retrace (i.e. you haven't already retrieved the necessary debuginfo packages and generated the full backtrace) available. If you do not have any, run a C or C++ application and crash it using {{command|kill -SIGSEGV (pid)}} or {{command|pkill -SIGSEGV (processname)}}
# Make sure you have ABRT crashes caught by CCpp (crashes in C and C++ applications) that need retrace (i.e. you haven't already retrieved the necessary debuginfo packages and generated the full backtrace) available. If you do not have any, run a C or C++ application and crash it using {{command|kill -SIGSEGV (pid)}} or {{command|pkill -SIGSEGV (processname)}}
|actions=
|actions=
# Run {{command|abrt-gui}} and select a binary crash
# Run {{command|abrt-gui}} and select a binary crash
# On Analyze step select <tt>Retrace Server</tt>. If GUI shows reporting selector instead of analyze selector (this happens if you already have the backtrace), select any reporter and click "Regenerate backtrace" button in the next window. This will bring you to analyzer selector
# GUI should ask whether you want to upload core to a remote server, answer YES.
# Wait until the job is finished
# Wait until the job is finished
# Continue with reporting
# Continue with reporting
# Not all distributions are supported. For example, trying to retrace Fedora 13 crash will result into an error.
# Not all distributions are supported. For example, trying to retrace Fedora 13 crash will result into an error.
# If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from GUI report window, or retrieved from event_log file in problem data directory (e.g. {{filename|/var/spool/abrt/ccpp-2011-03-04-15:46:26-22496/event_log}})
# If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from GUI report window, or retrieved from event_log file in problem data directory (e.g. {{filename|/var/tmp/abrt/ccpp-2011-03-04-15:46:26-22496/event_log}})
|results=
|results=
# The backtrace should be generated and it should good quality (all relevant symbols should be present - except for {{command|__kernel_vsyscall}})
# The backtrace should be generated and it should good quality (all relevant symbols should be present - except for {{command|__kernel_vsyscall}})
}}
}}
[[Category:Package_abrt_test_cases]]
[[Category:Package_abrt_test_cases]]

Latest revision as of 12:59, 3 May 2013

Description

This test case tests Retrace Server's integration into ABRT GUI.

Setup

  1. Ensure you have the plugin installed with the following command:
    • su -c 'yum install abrt-retrace-client'
  2. Make sure you have ABRT crashes caught by CCpp (crashes in C and C++ applications) that need retrace (i.e. you haven't already retrieved the necessary debuginfo packages and generated the full backtrace) available. If you do not have any, run a C or C++ application and crash it using kill -SIGSEGV (pid) or pkill -SIGSEGV (processname)

How to test

  1. Run abrt-gui and select a binary crash
  2. GUI should ask whether you want to upload core to a remote server, answer YES.
  3. Wait until the job is finished
  4. Continue with reporting
  5. Not all distributions are supported. For example, trying to retrace Fedora 13 crash will result into an error.
  6. If reporting is unsuccessful, please include the reporting log in your abrt bug report. Reporting log can be cut and pasted from GUI report window, or retrieved from event_log file in problem data directory (e.g. /var/tmp/abrt/ccpp-2011-03-04-15:46:26-22496/event_log)

Expected Results

  1. The backtrace should be generated and it should good quality (all relevant symbols should be present - except for __kernel_vsyscall)
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Retrace_Server_GUI&oldid=335241"