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
If a project has <DebugType>full</DebugType>, and it is compiled on Windows, it will have a full Windows PDB debug file generated. Sentry CLI knows how to deal with these, but we still need to be able to send a debug_id at runtime to match.
Presently, we are not sending any debug_id except for portable PDB format. We need to also send it when a full PDB was built.
This is reproducible on Sentry.Samples.Console.
dotnet run --project samples\Sentry.Samples.Console.Basic -f net48 -p:DebugType=full
Same for net6.0. (It's not specific to .NET Framework.)
Expected Result
The debug_id should be sent. Symbolication and source context should work.
Actual Result
The debug output will contain:
Info: Skipping DebugImage for module 'Sentry.Samples.Console.Basic.exe' because DebugId couldn't be determined
The event is missing a debug_id. Symbolication and source context does not work.
The text was updated successfully, but these errors were encountered:
Package
Sentry
.NET Flavor
Any
.NET Version
Any
OS
Windows
SDK Version
3.29.0
Steps to Reproduce
If a project has
<DebugType>full</DebugType>
, and it is compiled on Windows, it will have a full Windows PDB debug file generated. Sentry CLI knows how to deal with these, but we still need to be able to send adebug_id
at runtime to match.Presently, we are not sending any
debug_id
except for portable PDB format. We need to also send it when a full PDB was built.This is reproducible on Sentry.Samples.Console.
Same for
net6.0
. (It's not specific to .NET Framework.)Expected Result
The
debug_id
should be sent. Symbolication and source context should work.Actual Result
The debug output will contain:
The event is missing a
debug_id
. Symbolication and source context does not work.The text was updated successfully, but these errors were encountered: