-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Missing mangling in stack trace #873
Comments
This looks more like a problem with symbolication. I'm going to transfer this issue to the main repo. This could be related to getsentry/sentry#79268. |
Auto-routing to @getsentry/product-owners-issues for triage ⏲️ |
Routing to @getsentry/product-owners-issues-source-maps for triage ⏲️ |
Routing to @getsentry/product-owners-processing for triage ⏲️ |
Indeed, the current swift demangler in |
Platform
macOS
Environment
Production
Installed
Swift Package Manager
Version
8.38.0
Xcode Version
16.0
Did it work on previous versions?
No response
Steps to Reproduce
One stack frame is not demangled:
The stack trace line number referes to
try value(for: attribute, as: [AXUIElement].self)?.map { T($0) } ?? []
inSo it could be missing handling of mangling for nested protocols or typed throws.
Expected Result
I expected the stack frames be properly demangled.
Actual Result
Stack trace: https://sindresorhus.sentry.io/share/issue/784ced2af05b481d864831afb7c66548/
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: