Re: [Gems-users] failed assertion 'index < m_size'

[Dan Gibson <degibson@xxxxxxxx>]

This kind of assertion failure is usually due to some misconfiguration 
in rubyconfig.defaults or in the parameters provided to Ruby at runtime. 
Have you made changes to any parameters?
Regards,
Dan Gibson

Hemayet Hossain wrote:

> Hi Everybody,
> I was trying to use Ruby module (gems 1.3) with simics 2.2.19 (64 bit).
> I compiled the ruby with MOSI_SMP_bcast protocol and loaded the module 
> in simics having the solaris 9 disk image. After loading I continued the 
> execution (by "c" ) and immediately found the following error message. 
> Can anybody tell me why is tha happening or what should I do?
> Thanks a lot.
> ---------------
> Hemayet Hossain
> -------------------------------------------------
> successful installation of the ruby timing model.
> Ruby Timing Mode
> Warning: optimizations not enabled.
> Creating event queue...
> Creating event queue done
> Creating system...
>  Processors: 8
> Creating system done
> Ruby initialization complete
> failed assertion 'index < m_size' at fn TYPE& Vector<TYPE>::ref(int) 
> [with TYPE = SimicsProcessor*] in ../common/Vector.h:168
> failed assertion 'index < m_size' at fn TYPE& Vector<TYPE>::ref(int) 
> [with TYPE = SimicsProcessor*] in ../common/Vector.h:168
> At this point you might want to attach a debug to the running and get to the
> crash site; otherwise press enter to continue
> PID: 3955
> -------------------------------------------------------------
>
> _______________________________________________
> 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.
>
>
>