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

Allow specifying how many frames to pull in when creating a bucket #852

Open
pyoor opened this issue Oct 13, 2022 · 1 comment
Open

Allow specifying how many frames to pull in when creating a bucket #852

pyoor opened this issue Oct 13, 2022 · 1 comment

Comments

@pyoor
Copy link
Contributor

pyoor commented Oct 13, 2022

When creating a new bucket, it would be nice to specify how many frames to pull in from the initial crash to create the signature. Often times stacks in rust bugs have a lot of common code at the top of the stack.

@jschwartzentruber
Copy link
Contributor

jschwartzentruber commented Oct 14, 2022

There are a number of hidden URL parameters to /crashmanager/signatures/new/ we should expose in UI:

stackframes=int
forcecrashaddress=0, 1
forcecrashinstruction=0, 1

Regarding Rust backtraces, if you see patterns to the common code in your crashes, you can add a rule here to increase the default:

elif any(
entry.startswith("std::panicking") or entry.startswith("alloc::alloc")
for entry in crashInfo.backtrace
):
# rust panic adds 5-6 frames of noise at the top of the stack
maxStackFrames += 6

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

2 participants