-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
External Exception E0434352 using netcore #130
Comments
@phillsonntag, Did you try with rebasing system object? See also related #125. |
Yes, recent 2 years have been very difficult for me :( And it was very difficult to combine all that with opensource activities. Really hard for my time and generally for me personally. But I really like that all this are still helpful, and I still can continue develop something like this. Who follows me also knows that I had plan (and still have, see related #90) for native implementation. But today we're still using this through ilasm and through my custom assembler features for .NET Core support, as you can see. Well, time will tell. I'm still alive and this is good point to continue develop something in OSS and at all :) I want to thanks again to all who supported me! Thank you, guys! This project personally aggregated a bit of sum (especially when comparing with stars on github with my other projects). For all this years it was just about $80 for DllExport :) Soon I will try count this in details and personally donate to Robert and Cecil project something from that amount. |
I've just checked your examples. Thanks for the detailed report information! I really appreciate it because it really helps to save a bit of time in attempts to reproduce problem. So, I don't see the problems when rebasing system object. Thus, please consider use the related option. Details in #125 as I mentioned above. Let me know if you have other problems. Thanks! |
ah yes: typedef int(__stdcall *f_funci)(); FYI: We're using __cdecl by default for any exports! For __stdcall you need to configure DllExport attribute. |
Finally! It works, thank you very much for your help. The rebase did it. I missed something, but it finally works now. THANKS! :D EDIT: I also tried to define the stdcall before, but it didn't work either, so I tried everything I could find :D |
FYI: When I explicitly define Cdecl in the DllExport attribute, and import it in C++ via StdCall it also works. I don't know if this is wanted behaviour. |
Good!
For your case above it does not matter:
Calling convention just declares the rules for how to use stack, registers, arguments between calling; Mainly, who cleans the stack and how arguments are passed. Please read MSDN for details. |
Hello,
I'm currently struggling with the implementation of an exported .NET Core function in my Delphi application. Just before I submitted this issue I also tried to implement the same dll with the same function in C++.
Both implementations threw the same error
0xE0434352
.When I inspect the dll using a dependency inspector, the right dependencies are set and the function is correctly exported.
v1.7beta3
:x86, x64
andDirect-Mod/Cecil
in all possible variants.Used configuration:
Source
ExportsDemo.dll -> Exports.cs:
ExportsDemo -> ExportsDemo.csproj
C++ Project (PlusPlusDemo):
(I don't really know the syntax of C++, just wanted to make sure the exception doesn't belong to Delphi.)
Logs
C++ Exception:
Unhandled exception at 0x00007FFB9336A839 (KernelBase.dll) in PlusPlusDemo.exe: 0xE0434352 (parameters: 0xFFFFFFFF80070002, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x00007FFB85F00000).
C++ CallStack:
Output of Delphi using the Visual Studio Debugger:
VS2019_Delphi.log
Thank you in advance for the time and effort you put in this project.
The text was updated successfully, but these errors were encountered: