From Fedora Project Wiki
(clean ups) |
No edit summary |
||
| (5 intermediate revisions by 4 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= | ||
# 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 | ||
# | # 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 | # 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/ | # 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 symbols should be present) | # 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
- Ensure you have the plugin installed with the following 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
kill -SIGSEGV (pid)orpkill -SIGSEGV (processname)
How to test
- Run
abrt-guiand select a binary crash - GUI should ask whether you want to upload core to a remote server, answer YES.
- Wait until the job is finished
- Continue with reporting
- 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.
/var/tmp/abrt/ccpp-2011-03-04-15:46:26-22496/event_log)
Expected Results
- The backtrace should be generated and it should good quality (all relevant symbols should be present - except for
__kernel_vsyscall)