-
-
Notifications
You must be signed in to change notification settings - Fork 201
Description
Description
For some reports I have seen incorrect stacktraces. Seems to happen only for inlined functions,
and they are clearly wrong. It shows the same address, of the inlining function, for all those frames,
maybe some postprocessing done to the stacktrace?
Here's one example issue (hope this is not public?)
https://sentry.io/organizations/reason-studios/issues/1879135326
We use this to capture the stack trace:
sentry_event_value_add_stacktrace(event, nullptr, 0);
It's hard to know where things go wrong; in Sentry native or processing on the server or if our
symbols are wrong somehow, but I thought I'd report it in case you recognise the problem.
I have added our own stacktracing as attribute to our events to see if there's a difference.
When does the problem happen
- During build
- [? ] During run-time
- [? ] When capturing a hard crash
Environment
- OS: Only macOS so far (10.14, 10.15)
- Compiler: Xcode 11
- CMake version and config: [?, SENTRY_BACKEND=none]
Steps To Reproduce
Log output