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
Native AOT builds are really a native app and the stack traces come with instruction addresses. Therefore, to symbolicate this on Sentry, we need to append a list of debug images currently loaded, including the load address. We can either build this list manually by calling appropriate native platform-specific endpoints or use existing functionality from sentry-native. The latter seems like a better idea because in the future we may also want to use sentry-native for crash handling.
do we have integration tests to avoid regressions on this? I imagine something like the unity repo with the app getting launched then asserting on envelope sent
do we have integration tests to avoid regressions on this? I imagine something like the unity repo with the app getting launched then asserting on envelope sent
Native AOT builds are really a native app and the stack traces come with instruction addresses. Therefore, to symbolicate this on Sentry, we need to append a list of debug images currently loaded, including the load address. We can either build this list manually by calling appropriate native platform-specific endpoints or use existing functionality from
sentry-native
. The latter seems like a better idea because in the future we may also want to use sentry-native for crash handling.Related: #2247 and #2692
The text was updated successfully, but these errors were encountered: