I imagine that your jumping to a i/o device or a bad-address responder in the memory system and trying to access it with a cache block sized request. You should be able to figure out what's gone wrong with some trace flags, but if you want to get gdb attached at cycle 0 just set rgdb_wait in sim/system.cc to a positive integer.
Ali On 07.03.2012 05:55, Samuel Hitz wrote: > Hi there, > When I run gem5 with my kernel I get > > panic: invalid access size! > @ cycle 0 > [write:build/ARM/dev/isa_fake.cc, line 116] > What could be causing such an error? I assume it hasn't even started executing, since it's at cycle 0. > And how can I remote debug with gdb from the beginning? Basically I want to connect with gdb and then start executing code. > Help is much appreciated. > Best, > Samuel
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
