You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the Native SDK built with the breakpad backend and provoke a crash.
Let the SDK upload the minidump envelope on the next start.
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
Windows
Actual Result
There is no thread-context (register dump) in any of the threads for macOS:
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.
@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.
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
breakpad
backend and provoke a crash.minidump
envelope on the next start.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
Windows
Actual Result
There is no thread-context (register dump) in any of the threads for
macOS
:The uploaded
minidump
contains all registers for each thread. Also processing seems to work fine because theevent.json
also contains the registers (meaning theminidump
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 formacOS
in this configuration.Product Area
Issues
Link
https://sentry-sdks.sentry.io/issues/6075426538/events/e30a73a001b341972a3d1fa8cf49a949/?project=4506178389999616
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: