"xtime" cause segmentation fault

Topics related to running an idealized case
Post Reply
xyli00
Posts: 21
Joined: Wed Mar 18, 2020 5:39 pm

"xtime" cause segmentation fault

Post by xyli00 » Tue Jul 28, 2020 11:54 pm

Dear all,

I tried to invoke "xtime" in "module_radiation_driver.F" for some on-the-fly calculations.
I am using WRF Version 4.1.5 with an idealized case.

As a first step, I just added a simple print statement "print*, xtime" in "module_radiation_driver.F"
and got the segmentation error. I turned on "-traceback" flag so the error report points to the location
in "module_radiation_driver.F" where "print*, xtime" was entered.

taskid: 0 hostname: node004.local
module_io_quilt_old.F 2931 F
Quilting with 1 groups of 0 I/O tasks.
Ntasks in X 8 , ntasks in Y 12
WRF V4.1.5 MODEL
*************************************
Parent domain
ids,ide,jds,jde 1 201 1 201
ims,ime,jms,jme -4 32 -4 24
ips,ipe,jps,jpe 1 25 1 17
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 203794168 bytes allocated
med_initialdata_input: calling input_input
Input data is acceptable to use: wrfinput_d01
Timing for processing wrfinput file (stream 0) for domain 1: 10.98363 elapsed seconds
Max map factor in domain 1 = 0.00. Scale the dt in the model accordingly.
Timing for Writing wrfout_d01_2020-03-01_06:00:00 for domain 1: 11.73046 elapsed seconds
Timing for Writing auxhist2_d01_2020-03-01_06:00:00 for domain 1: 0.01432 elapsed seconds
WRF NUMBER OF TILES FROM OMP_GET_MAX_THREADS = 1
Tile Strategy is not specified. Assuming 1D-Y
WRF TILE 1 IS 1 IE 25 JS 1 JE 17
WRF NUMBER OF TILES = 1
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
wrf.exe 000000000CFEBCB3 Unknown Unknown Unknown
libpthread-2.12.s 000000360C20F7E0 Unknown Unknown Unknown
wrf.exe 000000000488708C module_radiation_ 4921 module_radiation_driver.f90
wrf.exe 00000000047E7D46 module_radiation_ 2455 module_radiation_driver.f90
libiomp5.so 00002AAAAF6199F3 __kmp_invoke_micr Unknown Unknown
libiomp5.so 00002AAAAF5DA5B2 __kmp_fork_call Unknown Unknown
libiomp5.so 00002AAAAF59AD60 __kmpc_fork_call Unknown Unknown
wrf.exe 000000000477B13A module_radiation_ 1040 module_radiation_driver.f90
wrf.exe 0000000004DA8FD9 module_first_rk_s 262 module_first_rk_step_part1.f90
wrf.exe 0000000003C063A6 solve_em_ 893 solve_em.f90
wrf.exe 000000000351288B solve_interface_ 123 solve_interface.f90
wrf.exe 0000000000584323 module_integrate_ 338 module_integrate.f90
wrf.exe 0000000000416B0A module_wrf_top_mp 325 module_wrf_top.f90
wrf.exe 0000000000415F59 MAIN__ 44 wrf.f90
wrf.exe 0000000000415EE2 Unknown Unknown Unknown
libc-2.12.so 000000360BA1ED5D __libc_start_main Unknown Unknown
wrf.exe 0000000000415DE9 Unknown Unknown Unknown


Any idea about this?

Attached please find my namelist.

Best regards,

Xiangyu
Attachments
namelist.input
(5.31 KiB) Downloaded 2 times

Ming Chen
Posts: 963
Joined: Mon Apr 23, 2018 9:42 pm

Re: "xtime" cause segmentation fault

Post by Ming Chen » Thu Jul 30, 2020 5:32 pm

xtime is a variable passed into radiation driver. You should be able to print it. How did you modify the code? Can you print this variable at the right beginning of the code, and see what happens?
WRF Help Desk

Post Reply

Return to “Idealized Cases”