d_hydro.exe has stopped working - Forum - Delft3D
Forum
- Home
- 3. Archive
- General
- Compilation on Windows
- d_hydro.exe has stopped working
d_hydro.exe has stopped working
d_hydro.exe has stopped working
Youngling Posts: 3 Join Date: 5/3/18 Recent PostsHi.
I successfully built source code on Win10 Pro, VS 2015 + Intel Parallel Studio XE 2018 Update after some manipulations:
- replacing flex.exe and byacc.exe with my own compiled on MSYS2
- changing FORTRAN configuration for more modern version
Also I ran all test and they were passed except one - 04_fluidmud
When I run this test it throws d_hydro.exe has stopped working.
So, I built debug version and created memory dump of crashing process using sysinternals procdump utility. Dump analyzing shows the next - https://snag.gy/zC5LhA.jpg
The problem is occurred in dio_shm_f2c_c.cpp
I will be appreciate if someone can help with this.
RE: d_hydro.exe has stopped working
Padawan Posts: 97 Join Date: 1/3/11 Recent PostsHi Kostia,
When running the FluidMud example on Windows, two instances of Delft3D-FLOW are launched that communicate with each other via a shared memory block. Looking at your screenshot, it seems that the creation of the shared memory block did not succeed. My guess is that the security settings on your machine are blocking this.
If you don't plan to use this FluidMud functionality, you better skip this example.
If you do plan to use this FluidMud functionality, try to run the example without using shared memory: open file "...\examples\04_fluidmud\dioconfig.ini" in a text editor and replace all occurrences of "StreamType=SharedMem" by "StreamType=ASCII".
Regards,
Adri
RE: d_hydro.exe has stopped working
Youngling Posts: 3 Join Date: 5/3/18 Recent PostsAdri, you have been right. I have changed StreamType to ASCII in dioconfig.ini under all Dataset section and it has executed successfully.
Thanks a lot for your help.
RE: d_hydro.exe has stopped working
Padawan Posts: 97 Join Date: 1/3/11 Recent PostsHi Kostia,
Good to hear it works.
The disadvantage of using ASCII instead of shared memory for the communication is that it is much slower.
Regards,
Adri