[FLASH-BUGS] more crashes

Andrew Siegel siegela at flash.uchicago.edu
Thu Jan 30 10:43:43 CST 2003


thanks for the additional info. The problem has been access to
a Compaq TRU64 compiler. however, I just got access to version5.5
so hopefully I can find the problem there and fix it quickly. andrew

On Thu, 30 Jan 2003, Sean Matt wrote:

> Hi,
> 
> 	We've recently noticed a problem with a standard setup that
> relates to the one we had with our own "evrard" setup.  Specifically, we
> used "setup sedov -auto -maxblocks=1000" to setup the standard 2d sedov
> problem.  We compiled it on Tru64 (OSF1 V5.1) using a Compaq
> fortran compiler (V5.5-1877-48BBF) without problems.  When we run (whether 
> on a single processor or multiple), the run crashes just after writing the 
> first output files.  The error we get is the same (and in the same place) 
> as we did for our own "evrard" setup, so the two are most likely related.  
> 	Previously, you mentioned that you were unable to reproduce the
> error.  We thought this may be more useful for you to work on than using
> the evrard setup we sent you.  In the sedov_2d_6lev.log file, the last few
> lines list no error messages, and are:
> 
>  [01-30-2003  11:06.35] <<< refined: tot_blocks =      69 >>>
>  [01-30-2003  11:06.35] *** checkpointed:  sedov_2d_6lev_hdf5_chk_0000
>  [01-30-2003  11:06.35] *** wrote 0069     blocks
>  [01-30-2003  11:06.35] *** plotfile: sedov_2d_6lev_hdf5_plt_cnt_0000
>  [01-30-2003  11:06.35] *** wrote to sedov_2d_6lev_hdf5_plt_cnt_0000
>  [01-30-2003  11:06.35] step       1  t=  0.000000E+00  dt= 1.000000E-10
> 
> The screen output gives the following error (this is similar for evrard):
> 
> ...
>   INITIAL TIMESTEP =   1.000000000000000E-010
>  *** Wrote output to sedov_2d_6lev_hdf5_chk_0000
>  number of variables found for plotfile storage =            3
>  dens pres temp
>  *** Wrote output to sedov_2d_6lev_hdf5_plt_cnt_0000 ***
> forrtl: error (75): floating point exception
> forrtl: error (75): floating point exception
>    0: for__issue_diagnostic [0x120335d28]
>    1: for__signal_handler [0x120334b90]
>    2: __sigtramp [0x1203ff2e0]
>    3: $modulemonot$monot_ [monot.F90: 68, 0x1200d3c10]
>    4: $moduleintrfc$intrfc_ [intrfc.F90: 253, 0x1200ba140]
>    5: $modulehydro_1d$hydro_1d_ [hydro_1d.F90: 275, 0x12008e930]
>    6: $modulehydrosweep$hydro_sweep_ [hydro_sweep.F90: 381, 0x1200a3550]
>    7: $hydro$hydro_3d_ [hydro.F90: 109, 0x120086e50]
>    8: evolve_ [evolve.F90: 69, 0x120084e40]
>    9: flash_    0: for__issue_diagnostic [0x120335d28]
>    1: for__signal_handler [0x120334b90]
>    2: __sigtramp [0x1203ff2e0]
>    3: $modulemonot$monot_ [monot.F90: 68, 0x1200d3c10]
>    4: $moduleintrfc$intrfc_ [intrfc.F90: 253, 0x1200ba140]
>    5: $modulehydro_1d$hydro_1d_ [hydro_1d.F90: 275, 0x12008e930]
>    6: $modulehydrosweep$hydro_sweep_ [hydro_sweep.F90: 381, 0x1200a3550]
> ... etc...
> 
> 




More information about the flash-bugs mailing list