bug fix in <NtFile>.Read(<length>), null is not 0 in RunFileCallSync #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the error I was getting
`
$file = Get-NtFile <some_path> -win32path
$file.read(5)
Exception calling "Read" with "1" argument(s): "(0xC000000D) - An invalid parameter was passed to a service or
function."
At line:1 char:187
`
I'm not a c# person and I didn't dive into if there are underlying problems beyond where I made my fix. While I would have expected null and 0 to be the same, they don't appear to be so I just made the lowest level fix that made sense to me.
let me know if you have any questions.