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
Several functions on the top of FAF backtraces are usually normalized and it means that those functions are not significant and not relevant to the crash.
The text was updated successfully, but these errors were encountered:
Currently the normalization "database" is stored in satyr: https://github.com/abrt/satyr/blob/master/lib/normalize.c
Satyr's Python API allows for normalization of whole stacktraces, so the only way to do this would be to diff the stacktrace before and after normalization, which seems inefficient. Definitely should be done offline and saved in the DB, possibly in the create-problems action as it loads and normalizes the stacktraces anyway.
Several functions on the top of FAF backtraces are usually normalized and it means that those functions are not significant and not relevant to the crash.
The text was updated successfully, but these errors were encountered: