Re: [Gems-users] Failed size assertion while simulating x86

[Gregory Byrd <gbyrd@xxxxxxxx>]

I've definitely seen that error, and I could never figure out why it happens.  Somehow, the "retry" from Simics after the memory operation is complete uses a different size (e.g., a byte read rather than a double word read).  I never saw any ill effects from just commenting out the assertion.

...Greg

On Thu, Sep 15, 2011 at 1:07 PM, abhisekpan@xxxxxxxxx <abhisekpan@xxxxxxxxx> wrote:

Hi,

I am simulating an x86-64 machine running linux on ruby.
I am getting the assertion failure error:

Ruby initialization complete
failed assertion 'm_active_requests[i].size == size' at fn int SimicsProcessor::lookupRequest(Address, CacheRequestType, int) in simics/SimicsProcessor.C:168
failed assertion 'm_active_requests[i].size == size' at fn int SimicsProcessor::lookupRequest(Address, CacheRequestType, int) in simics/SimicsProcessor.C: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: 16813

Abort (SIGABRT) in main thread
The simulation state has been corrupted. Simulation cannot continue.
Please restart Simics.

I commented the assertion out, and then it finishes execution. Please let me know if you have any idea why this is
happening, and what are the implications of commenting the assertion out. This issue  has been seen before:
https://www-auth.cs.wisc.edu/lists/gems-users/2009-May/msg00009.shtml
but I could not find a satisfactory solution!

Thanks a lot!

--
Abhisek
Live Long and Prosper

_______________________________________________
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.