You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Michal Toman edited this page Oct 31, 2013
·
3 revisions
Retracing is the process of determining unknown function names and associated source file name and line number to each stack frame. The process differs for every problem type (coredump requires the appropriate binaries and debuginfos, kerneloops requires the unstripped kernel modules, python does not require anything as it already outputs all the information within the stacktrace, ...), therefore it is managed by the problem plugin.
FAF's generic retracing algorithm consists of 3 steps:
Get the symbols that need retracing - get_ssources_for_retrace method
Find the associated packages (debuginfos, binaries, sources) - find_packages_for_ssource method
Execute the retrace when everything is ready - retrace method
The retrace process itself is controlled by a single action retrace.