admin/yamakadi-clroxide
1
0
Fork 0
mirror of https://github.com/yamakadi/clroxide synced 2026-06-08 18:28:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7 from yamakadi/yamakadi-patch-1

Browse Source 
Update README.md
This commit is contained in:
YK
2023-04-03 13:00:02 +09:00
committed by GitHub
parent 214222d578 22d9c4c0ef
commit 0be0e0312d
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5
View File
@@ -32,6 +32,11 @@ Compiling for `i686-pc-windows-gnu` fails due to known issues with rust panic un
Although I haven't run into this issue myself, there might be cases where you need to specifically compile your assembly as `x64` instead of `Any CPU`.
## Design Constraints
`windows` crate had no type definitions for `mscoree.dll` until a few weeks ago. It looks like the definitions for `mscoree.dll` have made their way into the `windows` crate in version `0.48.0`. However, these definitions don't appear to be working correctly. Just as an example; a vtable entry that should point to a function within the CLR thread (let's say at address `0x7ffef16821a0`), somehow returns an address widely out of range (`0x750003cac9053b48`).
The `windows` crate does a lot of fancy stuff with vtables for safety, but ironically, these are likely causing the access violation above. Or something else is happening... I intended to use the official definitions for V2 to offload the maintenance burden, but this is a dealbreaker.
## Usage