Re: forrtl: severe (174): SIGSEGV due to output file.
- From: dpb <none@xxxxxxx>
- Date: Mon, 04 Aug 2008 13:00:43 -0500
habzone2007@xxxxxxxxx wrote:
....
It looks like the initial time-step I am giving is little large and so
the initial parameters
calculated seems to have large errors. This does not show immediately
because it takes sometime for
the error to accumulate but after sometime, the code
derails and spits out " forrtl: severe (174): SIGSEGV" error. I
experimented with smaller time steps and it works fine now.
....
In line w/ Glenn's comment if you don't know (rather than know and just didn't say) what the actual error is and precisely where rather than just the symptoms it would seem appropriate to use the compile w/ debug options to track that down and add some error checking. Also, if there's a way to tell the initial time step is excessively large by computing an error estimate it would also seem appropriate and worthwhile to add something along those lines to identify it early on as Glenn says.
--
.
- Follow-Ups:
- References:
- forrtl: severe (174): SIGSEGV due to output file.
- From: habzone2007
- Re: forrtl: severe (174): SIGSEGV due to output file.
- From: Gordon Sande
- Re: forrtl: severe (174): SIGSEGV due to output file.
- From: habzone2007
- Re: forrtl: severe (174): SIGSEGV due to output file.
- From: habzone2007
- Re: forrtl: severe (174): SIGSEGV due to output file.
- From: dpb
- Re: forrtl: severe (174): SIGSEGV due to output file.
- From: glen herrmannsfeldt
- Re: forrtl: severe (174): SIGSEGV due to output file.
- From: habzone2007
- Re: forrtl: severe (174): SIGSEGV due to output file.
- From: habzone2007
- forrtl: severe (174): SIGSEGV due to output file.
- Prev by Date: Re: forrtl: severe (174): SIGSEGV due to output file.
- Next by Date: Re: forrtl: severe (174): SIGSEGV due to output file.
- Previous by thread: Re: forrtl: severe (174): SIGSEGV due to output file.
- Next by thread: Re: forrtl: severe (174): SIGSEGV due to output file.
- Index(es):