[SIGSEGV: Segmentation fault] when running SWAN only

Report or discuss software problems and other woes

Moderators: arango, robertson

Post Reply
Message
Author
remit
Posts: 15
Joined: Mon Jun 21, 2021 12:40 pm
Location: bmkg

[SIGSEGV: Segmentation fault] when running SWAN only

#1 Unread post by remit »

Dear community,

I have managed to compile SWAN and generate a swanM file with the following cpp file settings

Code: Select all

#define SWAN_MODEL
but when i do the command:

Code: Select all

mpirun -np 1 ./swanM BELAJAR_swan.in
error appears as follows:

Code: Select all

--------------------------------------------------------------------------------
 Model Input Parameters:  ROMS/TOMS version 4.1
                          Wednesday - December 7, 2022 - 11:39:25 AM
--------------------------------------------------------------------------------

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x7f6985cdead0 in ???
#1  0x7f6985cddc35 in ???
#2  0x7f698586751f in ???
#3  0x559cbe062c59 in ???
--------------------------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun noticed that process rank 0 with PID 0 on node LAPTOP-U4JKE22G exited on signal 11 (Segmentation fault).
--------------------------------------------------------------------------
I really appreciate the suggestions and solutions..thank you

swanM: https://1drv.ms/u/s!AlaANJ5cRpGZlqVFzwj ... g?e=mhG8AO
Attachments
BELAJAR_swan.in
(33.53 KiB) Downloaded 121 times
swan_bash.bash
(21.36 KiB) Downloaded 121 times

jcwarner
Posts: 1171
Joined: Wed Dec 31, 2003 6:16 pm
Location: USGS, USA

Re: [SIGSEGV: Segmentation fault] when running SWAN only

#2 Unread post by jcwarner »

this post is about SWAN, and it would best placed on the coawst ticket site
https://github.com/jcwarner-usgs/COAWST/issues
as a short reply, you need to look at any Err* or PRINT* files for more info.
if you are going to follow up, post a new instance on the coawst issues.
-j

Post Reply