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
The native PDB writer has a size limit of 0x10000 for calls to ISymUnmanagedWriter::SetSymAttribute. The writer does not enforce this limit on calls to SetSymAttribute but rather in CloseMethod where it returns E_OUTOFMEMORY. That leads to us emitting errors like
error CS0041: Unexpected error writing debug information -- 'Insufficient memory to continue the execution of the program'
That is very difficult for customers and us to debug. To help with root causing these problems we should emit a better error in the compiler when we hit this limit. Specifically the error should take into account the 0x10000 limit and issue an error message that includes the name of the method that was being emitted when the limit was hit.
This has come up two times now: #73447 and an internal feedback ticket. Having this better error would've saved us significant time in tracking down the problem.
The text was updated successfully, but these errors were encountered:
jcouv
added
4 - In Review
A fix for the issue is submitted for review.
and removed
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Oct 2, 2024
The native PDB writer has a size limit of 0x10000 for calls to
ISymUnmanagedWriter::SetSymAttribute
. The writer does not enforce this limit on calls toSetSymAttribute
but rather inCloseMethod
where it returnsE_OUTOFMEMORY
. That leads to us emitting errors likeThat is very difficult for customers and us to debug. To help with root causing these problems we should emit a better error in the compiler when we hit this limit. Specifically the error should take into account the 0x10000 limit and issue an error message that includes the name of the method that was being emitted when the limit was hit.
This has come up two times now: #73447 and an internal feedback ticket. Having this better error would've saved us significant time in tracking down the problem.
The text was updated successfully, but these errors were encountered: