We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
there is an error when building the driver
[MethodImpl(MethodImplOptions.InternalCall)] [RuntimeImport("ntoskrnl.exe", "DbgPrint")] public static extern ulong _DbgPrint(byte* Format, __arglist); static NTSTATUS DriverEntry() { _DbgPrint("%d".asstr(), __arglist(2)); return NTSTATUS.Success; } public static byte* asstr(this string str) { fixed (char* wc = str) { var buf = ExAllocatePool(PoolType.NonPagedPool, (ulong)str.Length + 20); for (int i = 0; i < str.Length; i++) buf[i] = (byte)wc[i]; buf[str.Length] = (byte)0; return buf; } }
build without any problems
ILC: AOT analysis error IL1005: testdriver.Program.DriverEntry(): Method will always throw because: Vararg call to 'UInt64 testdriver.WDK._DbgPrint(Char*)' not supported
No response
The text was updated successfully, but these errors were encountered:
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Sorry, something went wrong.
varargs are supported only on Windows for C++/CLI compatibility. C++/CLI is not supported by NativeAOT.
More general support for varargs is tracked by #48796.
Listed in #69919
I hope to support it soon. thanks.
No branches or pull requests
Description
there is an error when building the driver
Reproduction Steps
Expected behavior
build without any problems
Actual behavior
ILC: AOT analysis error IL1005: testdriver.Program.DriverEntry(): Method will always throw because: Vararg call to 'UInt64 testdriver.WDK._DbgPrint(Char*)' not supported
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: