NullReferenceException is not producing any helpful information for releases

[Kokujou]

This issue is now persistent for a very long time and caused a lot of problems in a project i'm working on.
Everytime a NullReferenceException occurs it never says anything about the parameter name the exception was thrown on.
Dpeending on the quality of the code this can cause really huge issues for testing and reproducing reported errors.

i know when you're debugigng code the debugger tells you what variable it is, but for release this information is not accessible.

i think it would benefit a lot of developers if this exception would generate a better error message, especially since the NullReferenceException is always bound to a parameter.

i didn't see any similar issues filed, so i hope this will get processed

[ghost]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This issue is now persistent for a very long time and caused a lot of problems in a project i'm working on.
Everytime a NullReferenceException occurs it never says anything about the parameter name the exception was thrown on.
Dpeending on the quality of the code this can cause really huge issues for testing and reproducing reported errors.

i know when you're debugigng code the debugger tells you what variable it is, but for release this information is not accessible.

i think it would benefit a lot of developers if this exception would generate a better error message, especially since the NullReferenceException is always bound to a parameter.

i didn't see any similar issues filed, so i hope this will get processed

Author:	Kokujou
Assignees:	-
Labels:	area-Diagnostics-coreclr, untriaged
Milestone:	-

[EgorBo]

Duplicates #3858

[mangod9]

Closing as dupe of #3858 as mentioned above.