The stack trace is not collected correctly when capturing a message or event
etelyatn opened this issue · 3 comments
Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which version of the SDK?
0.15.1
How did you install the package? (Git-URL, Assetstore)
Git
Which version of Unreal?
5.3.2
Is this happening in Unreal (editor) or on a player like Android, iOS, Windows?
Linux, Pixel streaming
Steps to Reproduce
Capture a message
SentrySubsystem->CaptureMessage(Message, ESentryLevel::Error);
or an event
USentryEvent* Event = NewObject<USentryEvent>();
Event->SetMessage(Message);
Event->SetLevel(ESentryLevel::Error);
Expected Result
Get the stack trace up to the Captured Message/Event
Actual Result
Always the same stack trace ended with crashpad::Settings::InitializeSettings
Any logs or screenshots
@etelyatn Is this issue specific to the Linux pixel streaming configuration or do you observe similar behavior with other platforms/targets as well?
@etelyatn Is this issue specific to the Linux pixel streaming configuration or do you observe similar behavior with other platforms/targets as well?
Maybe, this only applies to Linux systems; I don’t have the opportunity to check on others
As @tustanivsky said, I think we should figure out if this is isolated to Linux, Pixel streaming
or happening on other platforms as well to properly prioritize this.