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

ref(proguard): Keep track of frame indices #1411

Merged
merged 2 commits into from Mar 21, 2024
Merged

Conversation

loewenheim
Copy link
Contributor

Symbolication can expand one raw JVM frame into multiple frames. When we return the symbolicated stacktraces, we want it to be possible to tell which symbolicated frames came from which raw frames. To this end, we add an index to frames that you need to pass in and that gets copied to the symbolicated frames.

Example: You send a stacktrace to Symbolicator containing frames with indices [0, 1, 3, 4] (frame 2 has been filtered out for one reason or another). Symbolicator expands frame 3 to 3 frames. Then you'll get back frames with indices [0, 1, 3, 3, 3, 4].

@loewenheim loewenheim requested a review from a team as a code owner March 20, 2024 11:03
@loewenheim loewenheim self-assigned this Mar 20, 2024
@loewenheim loewenheim requested a review from anonrig March 20, 2024 14:53
///
/// When returning frames in a `CompletedJvmSymbolicationResponse`, all frames that were
/// expanded from the frame with index `i` will also have index `i`.
pub index: usize,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like an offset rather than an index, but I'm fine with both.

@loewenheim loewenheim merged commit acd9b39 into master Mar 21, 2024
10 checks passed
@loewenheim loewenheim deleted the proguard/frame_index branch March 21, 2024 07:22
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

Successfully merging this pull request may close these issues.

None yet

3 participants