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

macOS minidumps from breakpad do not render thread context(registers) #81173

Open
supervacuus opened this issue Nov 21, 2024 · 4 comments
Open

Comments

@supervacuus
Copy link
Contributor

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

  1. Use the Native SDK built with the breakpad backend and provoke a crash.
  2. Let the SDK upload the minidump envelope on the next start.
  3. in the web-ui: inspect the registers above the stack-traces of any of the threads in that event/issue (see attached event link).

Expected Result

I would expect to see the registers of at least the crashing thread and ideally of all threads. This works when a breakpad minidump is uploaded from Windows or Linux:

Linux

Image

Windows

Image

Actual Result

There is no thread-context (register dump) in any of the threads for macOS:

Image

The uploaded minidump contains all registers for each thread. Also processing seems to work fine because the event.json also contains the registers (meaning the minidump was correctly parsed and the data was transferred to the event). So this is neither a client-side or a processing issue, but seemingly the registers aren't rendered for macOS in this configuration.

Product Area

Issues

Link

https://sentry-sdks.sentry.io/issues/6075426538/events/e30a73a001b341972a3d1fa8cf49a949/?project=4506178389999616

DSN

No response

Version

No response

@getsantry
Copy link
Contributor

getsantry bot commented Nov 21, 2024

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

@snigdhas snigdhas transferred this issue from getsentry/sentry Nov 21, 2024
@kahest
Copy link
Member

kahest commented Nov 21, 2024

@snigdhas we think that this is an issue on the product side. For context, @supervacuus is the main maintainer of the Native SDK and we verified that the erroneous behavior is not caused by the SDK, and it also doesn't seem to be a Processing issue, as described in the issue.

@kahest kahest transferred this issue from getsentry/sentry-native Nov 22, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Nov 22, 2024

Routing to @getsentry/product-owners-issues for triage ⏲️

@getsantry
Copy link
Contributor

getsantry bot commented Nov 22, 2024

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting for: Product Owner
Status: Needs Discussion
Development

No branches or pull requests

2 participants