Re: Re: NIF calls to enif_fprintf causing segfaults on Windows

Are you running erlang with werl.exe?
In this case Erlang is started as a Windows application (not a console one)
and writing to stdout will not have any effect. If this is the case, try to
run your app with erl.exe

What version of MSVC did you use to build your NIF? Keep in mind that MSVC
2015-2019 have a common CRT, anything older has its own separate
incompatible CRT. So you may run into a similar problem where you have 2
MSVC CRTs loaded in your app, which don't play nice together. Sharing
non-trivial data between MSVC CRT implementations is considered undefined.

Erlang 24.x is built with MSVC 2019, so it is using the common 2015-2019 CRT

Jaka


On Tue, 27 Jul 2021 at 15:25, Brett Hemes <[email protected]> wrote:

> Interesting...  so I put together a Windows native make file to use cl.exe
> (vs gcc) from within a Visual Studio developer prompt and in this scenario
> the segfaults are gone but I don’t get any output to the terminal at all.
>
>
>
> Brett
>
>
>
> *From:* Jaka Bac <[email protected]>
> *Sent:* Tuesday, July 27, 2021 6:32 AM
> *To:* Brett Hemes <[email protected]>
> *Cc:* [email protected]
> *Subject:* [EXTERNAL] Re: NIF calls to enif_fprintf causing segfaults on
> Windows
>
>
>
> Just thinking out loud...
>
>
>
> Is the segfault a null pointer dereference?
>
> It is possible that stdout is not what MinGW runtime expects it to be and
> is possibly null.
>
> Windows Erlang is built by MSVC and it will run the MSVC CRT
> initialization code (which will set up stdout). Your NIF DLL is built by
> MinGW. And its CRT initialization possibly did not run or did not run
> correctly which in turn leaves the MinGW stdout undefined.
>
>
>
> Jaka
>
>
>
> On Mon, 26 Jul 2021 at 23:27, Brett Hemes <[email protected]> wrote:
>
> I have recently moved from a Linux environment to Windows and my NIFs that
> call `enif_fprintf` are causing segfaults.
>
>
>
> A simple call such as `enif_fprintf(stdout, “Hello, world!\n”);` will
> cause issue.
>
>
>
> My build setup is:
>
> * Windows 10
>
> * rebar3
>
> * MSYS2 + MinGW 64-bit + gcc
>
>
>
> I have tried in both `erl` and `werl` to the same effect as well as
> `stdout` and `stderr`...
>
>
>
> Does anyone have any insight into what might be the issue?
>
>
>
> Thanks,
>
> Brett
>
>