Re: [Gems-users] Ruby initialization fails in simics 3.0.18

[Mike Marty <mikem@xxxxxxxxxxx>]

Your checkpoint has 8 processor objects, right?

--Mike


> Hi,
>         I am trying to initialize the ruby module with ruby0.init in
> simics 3.0.18. But the initialization fails because of a segementation
> fault:
>
> Turning I-STC off and flushing old data
> Turning D-STC off and flushing old data
> successful installation of the ruby timing model.
> Ruby Timing Mode
> Creating event queue...
> Creating system ...
>     Processors : 8
> Segmentation fault (SIGSEGV) in main thread.
> The simulation state has been corrupted. Simulation cannot continue.
>
>            I traced the calls and the assertion in
> pc_step_t SIM_step_count(conf_object_t *p) { assert(0); return 0; };
> //fails for the processor 1. This function is being called by
> integer_t SIMICS_get_insn_count(int cpuNumber)
> {
>   processor_t* cpu = SIM_proc_no_2_ptr(cpuNumber);
>    return SIM_step_count((conf_object_t*) cpu);
>
> }
>
> Processor 0 gets initialized fine.
>
>                             I appreciate all your help.
>
> thanks,
> Mishali
> _______________________________________________
> 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.
>