sentry-cli uploading PDBs fails when symbols embedded
See original GitHub issueIn the Portable PDB PR: https://github.com/getsentry/sentry-dotnet/pull/2050
An error happens on the Sentry.dll
because of missing pdb.
Even though it’s possible some DLLs won’t have PDBs, it doesn’t mean debug info isn’t available.
In the case of Sentry.dll
, the debug information is embedded in the DLL itself:
We need to be able to read the debug info from the DLL and upload that to Sentry to support line numbers/paths.
Issue Analytics
- State:
- Created 10 months ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Sentry-cli hangs on uploading pdb - SDKs
The cli tool will always upload a pdb to Sentry.io, but sometimes it will hang indefinitely on the last “processing” stage. cmd: sentry-cli...
Read more >Native Crash Reporting: Symbol Servers, PDBs, and SDK ...
Since Sentry downloads debug files automatically, there is no longer the need to upload them with sentry-cli . This will likely shave some...
Read more >Source - GitHub
(#1468) - feat: extract and upload embedded Portable PDB from PE (#1463) ... uploading executables and debug symbols in one go (#412) ##...
Read more >dataset-labels-top3-30k-real.txt - Microsoft .NET
That fails, I believe due to the misplaced commas, I believe. You can see the if you open the file in an editor,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
closed via https://github.com/getsentry/sentry-cli/pull/1463 and will be available in the next CLI release
Note, with #2166 this issue no longer affects the Sentry .NET SDKs. However, it could still affect a user if they are embedding symbols in their own project, so we should keep this issue open until we have an updated Symbolic + Sentry CLI that handles it.