Re: [Gems-users] Segment Fault when calling dump-stats

[Xuan Qi <xqi@xxxxxxxxxxx>]

Thanks for the advices. I have fixed the problem. BTW, i still got some 
error if I only ruby. It looks to me 
that ruby and opal have to be loaded and initialized together. Is it 
always the case? Thanks.
Best regards,
Xuan Qi
PHD Student
Department of Computer Science
The University of Texas at San Antonio


On Thu, 21 Feb 2008, Dan Gibson wrote:

> Thats a good theory, Berkin. I haven't tried loading opal but not calling
> init -- you could be right.
>
> Berkin Ozisikyilmaz wrote:
>
>  I also get this error. And I think what causes it is to load module opal and
> then not initialize and use it. I think once it opal is loaded it links with
> ruby and need to run opal. I am not sure though. I had asked about this an
> correctness of the simulation in this way but nobody has replied. 
>
> Regards,
> berkin
>
> -----Original Message-----
> From: gems-users-bounces@xxxxxxxxxxx [mailto:gems-users-bounces@xxxxxxxxxxx]
> On Behalf Of Dan Gibson
> Sent: 2008-02-21 18:14
> To: Gems Users
> Subject: Re: [Gems-users] Segment Fault when calling dump-stats
>
> At first glance, it seems to me you're incorrectly specifying the main 
> memory size to Ruby.
> 512MB = 536870912 bytes
>
> This could be the cause of your problem.
>
> Regards,
> Dan
>
> Xuan Qi wrote:
>
>
>  Hi everyone,
>
> I am a beginner of GEMS/simics. I installed solaris10 on a sarek machine
> with 2 cores and 512MB memory. I am trying to make the ruby and opal work 
> correctly now. I compiled them with MOESI_CMP_directory protocol. I use 
> the 
> following script to start the target machine and ruby:
> read-configuration 2core.conf
> cpu-switch-time 1
> instruction-fetch-mode instruction-fetch-trace
> istc-disable
> dstc-disable
> magic-break-enable
> load-module ruby
> load-module opal
> ruby0.setparam g_NUM_PROCESSORS 2
> ruby0.setparam g_MEMORY_SIZE_BYTES 524288
> ruby0.init
>
> After I run some simple program on the target machine, I call 
> ruby0.dump-stats. But, I always get this error message:
> Segmentation fault (SIGSEGV) in main thread
> The simulation state has been corrupted. Simulation cannot continue.
> Please restart Simics.
>
> I am wondering what could be the problem and where I should look at to fix
>
>
>  this problem. Is it because the inconsistency of ruby cache and simics 
> g-cache? BTW, do ruby and opal have to be loaded together? Thanks a lot!
> Best regards,
> Xuan Qi
>
> _______________________________________________
> 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!