This test case tests Retrace Server's integration into ABRT GUI.
- 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)
- You need to use the
retrace02.fedoraproject.org server to retrace F16 crashes. You can set the Retrace Server address via ABRT's "Event Configuration".
- Because of certificate hostname mismatch (
retrace.fedoraproject.org) you need to disable the certificate check. Add
--insecure option to
abrt-retrace-client line in
/etc/libreport/events.d/ccpp_retrace_event.conf so the line looks like
abrt-retrace-client batch --dir "$DUMP_DIR" --status-delay 10 --insecure &&. Keep in mind this disables all certificate errors handling, thus it is not a good idea to use coredumps that may contain sensitive data.
How to test
abrt-gui and select a binary crash
- On Analyze step select Retrace Server. 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
- 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.
- The backtrace should be generated and it should good quality (all relevant symbols should be present - except for