You're talking about SE mode, right? I think this is akin to a segmentation fault in a regular program. Essentially you're trying to access a virtual memory page for which the address is invalid. If there was a kernel running you'd take a page fault and the kernel would decide if you were allowed to access that VM page. If so, it would be allocated. If not, it would cause a segmentation fault. I'm not entirely sure what the conditions are for SE mode. You could probably replicate it simply by doing:
int *a =0; int b = *a; Typically this error comes out of the page table walk code/TLB code. On Mon, Feb 13, 2012 at 11:58 AM, Mahmood Naderan <[email protected]>wrote: > Hi, > Can someone clarify what does "tried to read/write to unmapped > address" exactly mean? > > How can I trace that error? How this error is produced? What are the > possibilities? > Is there a simple example (or code/assembly snippet) which shows this > error? > > thanks > -- > // Naderan *Mahmood; > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
