Skip to content
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

Exception.Message breaking in minidump analyses #37

Closed
rupreetg opened this issue Dec 26, 2015 · 0 comments
Closed

Exception.Message breaking in minidump analyses #37

rupreetg opened this issue Dec 26, 2015 · 0 comments

Comments

@rupreetg
Copy link

I am debugging a minidump using CLRMD and I am getting _firstChar as null in GetStringContents method in Desktop\heap.cs file. This causes to break the if condition and we get a Object null reference exception -
if(_firstChar.Type == null)

Commit: dee3908

In what scenario is _firstChar null (though I'll dig more into it as to why its null) but more important is should we be handling the scenario where we get _firstChar as null in the first place?

Because of this issue, I am not able to get Exception.Message working properly in my code. I can share the dump if required.

rupreetg referenced this issue Dec 26, 2015
In minidumps we had an issue where string offset fields would be found
but they could not actually get values.
rupreetg added a commit to rupreetg/clrmd that referenced this issue Dec 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants