[MITgcm-support] seg fault
Klymak Jody
jklymak at uvic.ca
Fri Mar 27 23:27:55 EDT 2009
Ooops
My apologies - the issue was that my data.obcs had too many entries on
the boundaries.
Odd that it would run while debugging, and other times too (I'm never
very careful to make the data.obcs have the correct dimensions.
Thanks, Jody
On Mar 27, 2009, at 6:08 PM, Klymak Jody wrote:
> Hi All,
>
> I'm getting the following during the first time step after I reduced
> my models resolution. Looks like a segmentation fault:
>
> I'd think I did something goofy in my data files, but if I run with
> debug level 2 the model runs fine.
>
> If I run with my old resolution the model runs fine.
>
> I checked my stack and it is unlimitted.
>
> Any ideas what the issue could be?
>
> Thanks Jody
>
> (OpenMPI, gfortran, OS X 10.5)
>
>
> Signal:11 info.si_errno:0(Unknown error: 0) si_code:1(SEGV_MAPERR)
> Failing at addr:0x6de554c0
> [0] func:0 libopal.0.dylib 0x094658b3
> opal_show_help_yy_scan_string + 515
> [1] func:1 libSystem.B.dylib 0x9540d2bb
> _sigtramp + 43
> [2] func:2 ??? 0xffffffff 0x0 +
> 4294967295
> [3] func:3 mitgcmuv 0x001da497
> do_oceanic_phys_ + 3303
> [4] func:4 mitgcmuv 0x001ed2fd
> forward_step_ + 397
> [5] func:5 mitgcmuv 0x0024cb84
> the_main_loop_ + 420
> [6] func:6 mitgcmuv 0x0024cdac
> the_model_main_ + 252
> [7] func:7 mitgcmuv 0x00197905 MAIN__ +
> 565
> [8] func:8 mitgcmuv 0x0025d718 main + 40
> [9] func:9 mitgcmuv 0x000017a6 start + 54
>
>
> --
> Jody Klymak
> http://web.uvic.ca/~jklymak/
>
>
>
>
>
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support
--
Jody Klymak
http://web.uvic.ca/~jklymak/
More information about the MITgcm-support
mailing list