Skip to content
New issue

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

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

Already on GitHub? # to your account

feat(protocol): Add protocol support for WASM #852

Merged
merged 6 commits into from
Nov 27, 2020
Merged

Conversation

mitsuhiko
Copy link
Member

@mitsuhiko mitsuhiko commented Nov 24, 2020

This extends the protocol for WASM. In the frame you can now provide addr_mode to override the behavior of an address. For instance one can set this to rel:index to set it relative to the index of a debug image. This is all handled in the background in sentry.

Refs getsentry/symbolicator#301

@mitsuhiko mitsuhiko marked this pull request as ready for review November 24, 2020 23:36
@mitsuhiko mitsuhiko requested a review from a team November 24, 2020 23:36
@@ -126,6 +126,9 @@ pub struct Frame {
/// then symbolication can take place.
pub instruction_addr: Annotated<Addr>,

/// Defines the addressing mode for addresses.
pub addr_mode: Annotated<String>,
Copy link
Member

Choose a reason for hiding this comment

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

We should consider validating the format here, but I think it's fine to merge as string.

@@ -377,13 +377,11 @@ pub struct NativeDebugImage {
/// Starting memory address of the image (required).
///
/// Memory address, at which the image is mounted in the virtual address space of the process. Should be a string in hex representation prefixed with `"0x"`.
#[metastructure(required = "true")]
Copy link
Member

Choose a reason for hiding this comment

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

Does this work with the sentry processor as is? I think we may expect non-null values at some places in native/processing.py or native/symbolicator.py.

Copy link
Member

Choose a reason for hiding this comment

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

Looked into this, and it will work. There are two places in AppleCrashReport rendering where we would throw None ValueErrors.

@jan-auer jan-auer merged commit 24b8524 into master Nov 27, 2020
@jan-auer jan-auer deleted the feature/wasm branch November 27, 2020 13:46
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants