Date: | Fri, 13 Feb 2009 14:55:25 -0600 |
---|---|
From: | Jayaram Bobba <bobba@xxxxxxxxxxx> |
Subject: | Re: [Gems-users] Ruby Segmentation Fault |
So I am completely baffled! It seems like there is some memory race and the values that the softwrea handler tries to write are lost. However, I though that the threadTransContext[threadID] structures are private per thread, so there shouldn't be any race problems!!!!I agree that a race should not occur. Could you try moving the randomized_backoff call to the end of the function so that the threadTransContext structures get updated right after the while loop. You might want to look and see if the simulator is passing the right threadID to the software handlers and if there are any stray simulator log writes from processor 2 to the log of the first thread. Jayaram |
Previous by Date: | Re: [Gems-users] new user of GEMS.... pls help, parijat shukla |
---|---|
Next by Date: | [Gems-users] Write-update protocol, Abdullah Kayi |
Previous by Thread: | Re: [Gems-users] Ruby Segmentation Fault, Konstantinos Nikas |
Next by Thread: | Re: [Gems-users] Ruby Segmentation Fault, Konstantinos Nikas |
Indexes: | [Date] [Thread] |