This is odd, really odd.
I tried the sample program you use with R.NET 1.5.10, both process types (64 and 32 bits) work just file. I have R 3.1.0 running on Win7 64 bits with the latest patches.
Thanks to the very useful tool CFF Explorer (my thanks to the author) I can check that indeed R_CStackDir is defined and exported. But R.NET does not try to access it (it does touch R_CStackLimit however). See image at the end.
Can you check out the latest onboarding guide? I just updated it to reference the latest public R.NET packages. I do not get any issues either. It is the best I can propose, in the hope the issue is gone for you. If indeed "something" tries to access R_Cstackdir with that capitalization (instead of R_CStackDir) then yes, there is a problem. But I have no idea what does and why this happens.
![R.dll export table]()
I tried the sample program you use with R.NET 1.5.10, both process types (64 and 32 bits) work just file. I have R 3.1.0 running on Win7 64 bits with the latest patches.
Thanks to the very useful tool CFF Explorer (my thanks to the author) I can check that indeed R_CStackDir is defined and exported. But R.NET does not try to access it (it does touch R_CStackLimit however). See image at the end.
Can you check out the latest onboarding guide? I just updated it to reference the latest public R.NET packages. I do not get any issues either. It is the best I can propose, in the hope the issue is gone for you. If indeed "something" tries to access R_Cstackdir with that capitalization (instead of R_CStackDir) then yes, there is a problem. But I have no idea what does and why this happens.
