FUTURE POSTS
- Partial writes, IO_Uring and safety - about one day from now
- Configuration values & Escape hatches - 5 days from now
- What happens when a sparse file allocation fails? - 7 days from now
- NTFS has an emergency stash of disk space - 9 days from now
- Challenge: Giving file system developer ulcer - 12 days from now
And 4 more posts are pending...
There are posts all the way to Feb 17, 2025
Comments
That's a good thing.
Error code, address and thread are useful hint's to start diagnosing, a full dump might have been better and perhaps the EE should try to create one upon blowing up (but that might be impossible).
Try to go in detail .you will find the exact cause of error.
Can be easy if you did only corrupt the stack and this is reproducible. But if you get this AccessViolation during a GC then it can become quite hard to get down to the root cause. In any case you need to check what did trigger the Exception. It can also be invalid IL generated by a Buggy code generator.
Comment preview