Segmentation fault once reads in boundary files (zeta,uvbar)

Sediment modeling collaborators: issues, applications, information exchange

Moderators: arango, robertson, rsignell

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

Segmentation fault once reads in boundary files (zeta,uvbar)

#1 Post by CeeCee.X » Tue Feb 17, 2015 11:20 pm

Hi, All,

I was wondering if anyone could give me some suggestions on experiencing segmentation fault when reads in 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 into consideration and it runs. The last two recognized the Input Boundary File 01: 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 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 00000039AD21ECDD Unknown Unknown Unknown
coawstG_tf 000000000041ADF9 Unknown Unknown Unknown

User avatar
Posts: 3704
Joined: Wed Jul 02, 2003 5:29 pm
Location: IMS/UAF, USA

Re: Segmentation fault once reads in boundary files (zeta,uv

#2 Post by kate » Tue Feb 17, 2015 11:37 pm

People invented debuggers to solve this sort of problem. I just don't know otherwise.

Post Reply