[Gems-users] Does this assertion fixed in new GEMS releases?

[Xuan Qi <xqi@xxxxxxxxxxx>]

Hi everyone,

My simulation crashes when using ruby and opal. I checked out
the previous threads and my problem is exactly same as this one:

failed assertion 'address < 0x100000000ull' at fn integer_t
SIMICS_read_physical_memory(int, physical_address_t, int) in
simics/interface.C:237
failed assertion 'address < 0x100000000ull' at fn integer_t
SIMICS_read_physical_memory(int, physical_address_t, int) in
simics/interface.C:237
At this point you might want to attach a debug to the running and
get

And the fix-up of this problem is:
"Your assertion should only occur if the DATA_BLOCK parameter, in
$GEMS/ruby/config/rubyconfig.defaults is set to "true", or you are
using the LogTM protocol.

We will fix this assertion in a minor update to the release in the
near future.  For now, you can comment out the assertion statement,
recompile, and it shouldn't cause any ill effects."

As this was posted back in 2006, I am wondering if this assertion has
been fixed in the new release or not? Should I still follow this post
to fix the crash problem? Thank you very much...

Best regards,
Xuan Qi
PHD Student
Department of Computer Science
The University of Texas at San Antonio