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
Incorrect stack traces for UWP in .NET Native #3316
Comments
I can't really debug this properly. It doesn't appear to be possible to substitute a project reference to Sentry.csproj for the NuGet package reference in the demo project provided. However I think I see what's causing this: sentry-dotnet/src/Sentry/Internal/DebugStackTrace.cs Lines 380 to 388 in 233e95b
In a UWP app, which is targeting .NET Framework, we do have AOT effectively for release builds (if This can be confirmed by capturing the debug info to a file:
You can see a bunch of in app frames get dropped there because we can't symbolicate these. Very tricky to resolve... especially since it's so difficult to debug (logging is pretty much the only weapon we have here). |
The reason why I added this issue to the other issue that was about trimming is because I think this issue is also related to trimming. When you're running the app then, the second line shows up in Sentry:
Maybe there's more use of reflection somwehere that causes this problem. Would this be the expected strack trace to show up anyways?
|
We might get some benefits out of having this merged? #3282 |
Additionally, maybe we should put a guard around enabling AOT on platforms where we know we don't properly support it. Just so users don't get surprised by unexpected outcomes. |
Scratching that. See #3343 (comment) |
Originally posted by @tipa in #3240 (comment)
Today I received another funny stack trace (it is the raw stack trace) - https://timopartl.sentry.io/issues/5216095235:
It's from a manually captured exception, but the crash report I was referring to in my last comment was from a crash (and also it was the raw stack trace), here's the link: https://timopartl.sentry.io/issues/5178256155
Here's another example project to reproduce the issue (run in Release mode). It logs the stack trace manually as breadcrumb, and this is what I see in the dashboard: Sentry_UWP.zip
stack trace:
stack trace from breadcrumb:
This is a very simple example so there's not a lot information missing, but I would at least expect to see the line
Sentry_UWP.SubPage.OnNavigatedTo(NavigationEventArgs)
. If you want me to, I can try to produce a crash that has a longer stack trace with more information missing. But I think even this small exmaple shows that there's something wrong.The text was updated successfully, but these errors were encountered: