Re: [mesa-users] Segfaults when running from photo

[Kent B. <kg...@la...>]

Ahh, that sounds like a real bug then.

On Thu, 2011-04-14 at 14:46 +0100, Warrick Ball wrote:
> Kent,
> 
> This is a fresh installation and I'm taking photos from the run I've done 
> only moments before (so the same version). Even if I clear the photos/
> directory to make sure a new photo is generated, I get the segfault.
> 
> W
> 
> On Thu, 14 Apr 2011, Kent Budge wrote:
> 
> > Warrick,
> >
> > The photo restarts aren't guaranteed to work across versions of MESA.
> >> From the "How to Use MESA" web page:
> >
> > "Also, it should be emphasized that the photos are not intended for
> > long-term storage of models—the ‘save_model_number’ scheme described
> > above is meant for that purpose. Instead the photos are intended for use
> > during one specific run. In particular, when you update to a new version
> > of MESA star, you should expect your existing photo files to become
> > obsolete. If you have a lengthy run in progress when you want to update
> > MESA, then you should do ‘save_model_number’ to save state before
> > starting the update, and then do ‘load_saved_model’ to resume the
> > evolution after you have done the update."
> >
> >
> > On Thu, 2011-04-14 at 14:11 +0100, Warrick Ball wrote:
> >> Hi,
> >>
> >> I've just successfully installed MESA revision 3190. When I compile with
> >> gfortran (GCC 4.5.2), it runs on all of the "first things to try", except
> >> for restarting from a previous photo. After the first suggested run, if I
> >> try
> >>
> >> ./re x050
> >>
> >> I get the output
> >>
> >> x050
> >> Revision: 3190
> >> Thu Apr 14 13:23:57 BST 2011
> >>   read extra star_job inlist1 from inlist_first_thing_to_try
> >>   read extra controls inlist1 from inlist_first_thing_to_try
> >>   read restart_photo
> >> ./re: line 28: 29003 Segmentation fault      ./star
> >> Thu Apr 14 13:24:00 BST 2011
> >>
> >> I've explored the operating scripts a bit but I really can't see what the
> >> problem is. I've recompiled from scratch and checked things like disk
> >> space too, just to be sure.
> >>
> >> When I compile using ifort (11.1), everything works as expected.
> >>
> >> Not sure what other information is useful. I'm on RHEL 5.6, x86-64 arch
> >> (Intel Core 2).
> >>
> >> Cheers,
> >> Warrick
> >>
> >
> 
--