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

Possible incorrect VA for clr.dll when debugging at runtime #79

Closed
3F opened this issue Jul 14, 2018 · 3 comments
Closed

Possible incorrect VA for clr.dll when debugging at runtime #79

3F opened this issue Jul 14, 2018 · 3 comments

Comments

@3F
Copy link
Owner

3F commented Jul 14, 2018

Reported by @davidsanda, in #77 (comment)

Possible exception:

Exception thrown at 0x00007FFAF53A2774 (clr.dll) in server_unittests.exe: 0xC0000005: Access violation reading location 0x0000000000000000
  • ... happens when calling a base constructor from a derived class.
@davidsanda
Copy link

I've taken a look at this in assembly and there is simply an unconditional call to unrecognized region of memory. I'll try to create a minimal project that reproduces it, but it is not that simple.

@davidsanda
Copy link

I nailed it in asm to some static asm call to reserved region of memory.

@3F
Copy link
Owner Author

3F commented Dec 15, 2019

@davidsanda, Please clarify the problem. Some related can be due to some incorrect processing in my custom assembler like this: #125 (comment)

Or something related to incorrect arch/types "requests" in heap. See my explanation through Java/JNA and C++ etc. Here or for Conari project.

It also can be due to incorrect instructions in certain official MS versions.

Thus, try to isolate problem via very simple code. Any project-sample would be really useful for quick inspection.

Thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants