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

Explore fingerprint matching for bugsnag stack trace #259

Open
kpgalligan opened this issue Jun 19, 2022 · 0 comments
Open

Explore fingerprint matching for bugsnag stack trace #259

kpgalligan opened this issue Jun 19, 2022 · 0 comments

Comments

@kpgalligan
Copy link
Collaborator

When we get a crash on bugsnag, the code writes the stack to our own json, then when the app starts up, if the ktcrash key matches the event, and there's only one error, we simply overwrite the stack with our stack. That's almost certainly fine, but I am worried that maybe that's not precise enough. This ticket is a reminder to dig into this later. We could try to do a "fingerprint match", where from main up until objc2kotlin should match function pointers exactly. However, I don't know if that buys us anything.

image

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

No branches or pull requests

1 participant