Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grey out normalized functions #395

Open
jfilak opened this issue Mar 2, 2015 · 1 comment
Open

grey out normalized functions #395

jfilak opened this issue Mar 2, 2015 · 1 comment

Comments

@jfilak
Copy link
Contributor

jfilak commented Mar 2, 2015

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.

@mbrysa
Copy link
Contributor

mbrysa commented Mar 2, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants