Re: [Gems-users] Checkpointing after roby/opal initialization

[Dan Gibson <degibson@xxxxxxxx>]

There seems to be a lot of confusion on the list about this recently. Let me make it clear:

* Taking checkpoints /after/ loading Ruby and/or Opal is NOT a good idea. As you can see from the output below, there is no guarantee that they will re-load correctly when you next read the checkpoint.

* If you MUST take a checkpoint after loading Ruby and/or Opal, then you must MANUALLY edit your checkpoint file, and remove all references to Ruby and Opal. After doing so, you should be able to load the checkpoint normally, then re-load Ruby/Opal.

Regards,
Dan

On Sun, May 17, 2009 at 9:16 PM, <soundara@xxxxxxxxxxx> wrote:

Hello,

I am trying to take a checkpoint after loading and initializing ruby and
opal modules. By I keep getting the following error messages. I looked at
an earlier message and tried removing timing_model: ruby 0 (when
checkpointing with ruby only) but still the error did not disappear.
Any ideas why?


Thank you,
Niranjan


Error:-

/***************************************************************************\
 > Physical Memory object cannot be found. If you are NOT compiling Ruby
and <
 > you see this message, something is wrong.
 <
 > This message is part of the normal compilation process.
 <
 \*************************************************

 /***************************************************************************\
 > Opal found no processors. If you are NOT compiling Opal and you see
this  <
 > message, something is wrong.
 <
 > This message is part of the normal compilation process.
 <
 \***************************************************************************/

_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.

-- 
http://www.cs.wisc.edu/~gibson [esc]:wq!