Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

real.exe Segmentation fault (core dumped)

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.


New member
Hi everyone!

As a result of executing compile, *.exe (ndown.exe, real.exe, wrf.exe, tc.exe) was created in the run directory. However, the namelist.input file was created, but it was not displayed in green. In other versions of WRF, the namelist.input file is marked in green, so I want to make sure that this version (WRFV4.2.2) is not wrong.
If ./real.exe is executed with the contents of the attached namelist.input file, "Segmentation fault (core dumped)" is displayed. At this time, the rsl.* file is not created. What's the matter?

Is there something wrong with the installation?
[※(dm+sm) INTEL (ifort/icc) installed]

A related file is attached.


  • configure.wrf
    23.1 KB · Views: 20
  • namelist.input
    5.1 KB · Views: 20
  • run_directory_namelist_color_check.JPG
    330.7 KB · Views: 206
  • .bash_profile.docx
    14.8 KB · Views: 21
Since you compiled the code with a dm+sm option, you will need to use some sort of MPI command to run the code. For e.g.,
mpiexec -np 1 ./real.exe

You cannot simply type "./real.exe." When running wrf.exe, you will also need to designate your threads, tasks, tasks-per-node, etc., as I've done in this example batch script for a dm+sm simulation (note - this script is asking for 1080 total processors, which is much more than you need).
#SBATCH --job-name=WRF_test
#SBATCH --nodes=30
#SBATCH --ntasks=120
#SBATCH --ntasks-per-node=4 
#SBATCH --cpus-per-task=9
#SBATCH --exclusive
ulimit -s unlimited
ulimit -c unlimited
mpiexec -np 120 ./wrf.exe

although real.exe should probably run with just a single processor.

If you aren't familiar with running with distributed and shared memory processing, it may be best to stick with a strictly distributed-memory (dmpar) compile, instead. We have seen many errors with dm+sm, and if it's not something you specifically need, it's probably easier to just use dmpar. You will still need to use the above syntax for running with dmpar, as well.

The color of the namelist.input file is specific to settings on your system. If you are able to modify and save the file, there isn't a problem with it.