Re: [Gems-users] rubu0.init step fails: how can I debug this:

[Dan Gibson <degibson@xxxxxxxx>]

Ataur,
I'm not sure how you might go about debugging it, actually. I'm not sure 
where the 'killed' message originates from... I can guess that it might 
be a segmentation fault, but that is only a guess.
The code that is executed by ruby0.init is in ruby/init.C, which calls 
several other places in the code. You can start either
1) attaching a debugger or
2) Inserting some print statements and flushes in init.C, and try to 
figure out where the problem resides.
Regards,
Dan

Forum Forum wrote:
> Hi Dan:
>
> I tried without those 2 commands and still if fails in the same point 
> - is there a way to debug why it is failing. I mean, can I look at 
> some files (log/etc) to see what is the reason it failed.
> Thanks,
>
> Ataur.
>
> [patwarya@chipdesign ~/GEMS]$   cd $GEMS/simics/home/MOSI_SMP_bcast
> [patwarya@chipdesign MOSI_SMP_bcast]$ ./simics -stall
>
> simics> read-configuration 
> /home/patwarya/GEMS/simics-2.2.19/home/firststeps/fs-config-5
> simics> dstc-disable
> Turning D-STC off and flushing old data
> simics> load-module ruby
> simics> ruby0.setparam g_NUM_PROCESSORS 1
> simics> ruby0.setparam g_MEMORY_SIZE_BYTES 4294967296
> simics> ruby0.init
> Ruby Timing Mode
> Creating event queue...
> Creating event queue done
> Creating system...
>   Processors: 1
> Killed
>
> [patwarya@chipdesign MOSI_SMP_bcast]$
>
> */Dan Gibson <degibson@xxxxxxxx>/* wrote:
>
>     x86 targets don't allow stalling of instruction fetch... can you
>     try again without the "instruction-fetch-mode
>     instruction-fetch-trace" and "istc-disable" steps?
>
>     Regards,
>     Dan
>
>     Forum Forum wrote:
> >     Hi:
> >
> >     I am using GEMS (Release 1.1 for GEMS and SIMICS 2.2)  for x86
> >     target/host machine in Linux  - I used the patch for x86.
> >
> >     I am following the quick steps as given in:
> >     http://www.cs.wisc.edu/gems/doc/wiki/moin.cgi/QuickStart
> >
> >     I used the checkpoint file which is taken from (I am not sure
> >     this has something to do with the failure that I am seeing):
> >     $GEMS/simics-2.2.19/home/firststeps/fs-config-1
> >
> >     I did the following commands and found the job to be killed after
> >     I applied ruby0.init command. The details are given below.
> >
> >     Please let me know how I can debug this or if I am not doing it
> >     right somewhere:
> >     --------------------------------------------------------------------------------------------------------------------
> >
> >     [patwarya@chipdesign MOSI_SMP_bcast]$ ./simics -stall
> >
> >     simics> read-configuration
> >     /home/patwarya/GEMS/simics-2.2.19/home/firststeps/fs-config-5
> >
> >     Then I got a pop-up window with title as:
> >     Simics Console: con0
> >
> >     The Debian GNU/Linux is booted.
> >
> >     Then I applied following commands:
> >
> >     simics> instruction-fetch-mode instruction-fetch-trace
> >
> >     simics> istc-disable
> >
> >     simics> dstc-disable
> >
> >     simics> load-module ruby
> >
> >     simics> ruby0.setparam g_NUM_PROCESSORS 1
> >
> >     simics> ruby0.setparam g_MEMORY_SIZE_BYTES 4294967296
> >
> >     simics> ruby0.init
> >     Ruby Timing Mode
> >     Creating event queue...
> >     Creating event queue done
> >     Creating system...
> >       Processors: 1
> >     Killed
> >
> >     [patwarya@chipdesign MOSI_SMP_bcast]$
> >                                          
> >     Thanks,
> >     Ataur.
> >     ------------------------------------------------------------------------
> >     Yahoo! Messenger with Voice. Make PC-to-Phone Calls
> >     <http://us.rd.yahoo.com/mail_us/taglines/postman1/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>
> >     to the US (and 30+ countries) for 2¢/min or less.
> >     ------------------------------------------------------------------------
> >
> >     _______________________________________________
> >     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.
> >
> >       
>     _______________________________________________
>     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.
>
>
> ------------------------------------------------------------------------
> Stay in the know. Pulse on the new Yahoo.com. Check it out. 
> <http://us.rd.yahoo.com/evt=42974/*http://www.yahoo.com/preview>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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!