Ocean Modeling Discussion

ROMS/TOMS

Search for:
It is currently Sat Jul 20, 2019 4:12 pm




Post new topic Reply to topic  [ 2 posts ] 

All times are UTC

Author Message
PostPosted: Tue Feb 17, 2015 11:20 pm 
Offline

Joined: Thu Jul 17, 2014 1:31 pm
Posts: 20
Location: PNNL, used to work and study at University of Florida
Hi, All,

I was wondering if anyone could give me some suggestions on experiencing segmentation fault when reads in bry.nc. The boundary conditions I used is for applying zeta and ubar/vbar at South,North,East boundaries. My idealized rectangular domain is closed at west. I'm using the Chapman/Flather combination for the depth-integrated mode and I undefined ana_fsobc and ana_m2obc in my cpp option. I already turned on debug when compiling the execute but the system didn't provide me any details and stopped as the following:


The first one didn't take bry.nc into consideration and it runs. The last two recognized the Input Boundary File 01: ocean_bry.nc but crushed when doing the following:

INITIAL: Configuring and initializing forward nonlinear model ...
*******

Metrics information for Grid 01:
===============================

Minimum X-grid spacing, DXmin = 2.00000000E+00 km
Maximum X-grid spacing, DXmax = 2.00000000E+00 km
Minimum Y-grid spacing, DYmin = 2.00000000E+00 km
Maximum Y-grid spacing, DYmax = 2.00000000E+00 km

Minimum barotropic Courant Number = 8.68685683E-02
Maximum barotropic Courant Number = 6.29106516E-01
Maximum Coriolis Courant Number = 8.00000000E-04

forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
coawstG_tf 00000000008D4CA9 Unknown Unknown Unknown
coawstG_tf 00000000008D3620 Unknown Unknown Unknown
coawstG_tf 000000000088ED92 Unknown Unknown Unknown
coawstG_tf 000000000084B1E3 Unknown Unknown Unknown
coawstG_tf 000000000084F1DB Unknown Unknown Unknown
libpthread.so.0 00000039ADE0F500 Unknown Unknown Unknown
coawstG_tf 0000000000752C5E Unknown Unknown Unknown
coawstG_tf 0000000000650CBA Unknown Unknown Unknown


I was wondering in this situation what could caused a segmentation fault?

Thanks a lot.
coawstG_tf 000000000060EF66 Unknown Unknown Unknown
coawstG_tf 0000000000539AD1 Unknown Unknown Unknown
coawstG_tf 000000000041E0EB Unknown Unknown Unknown
coawstG_tf 000000000041B971 Unknown Unknown Unknown
coawstG_tf 000000000041B193 Unknown Unknown Unknown
coawstG_tf 000000000041AF06 Unknown Unknown Unknown
libc.so.6 00000039AD21ECDD Unknown Unknown Unknown
coawstG_tf 000000000041ADF9 Unknown Unknown Unknown


Top
 Profile  
Reply with quote  
PostPosted: Tue Feb 17, 2015 11:37 pm 
Offline
User avatar

Joined: Wed Jul 02, 2003 5:29 pm
Posts: 3633
Location: IMS/UAF, USA
People invented debuggers to solve this sort of problem. I just don't know otherwise.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group