Are you running in full-system mode? This could indicate a kernel panic on your simulated system. We trap the panic call and generate a break event, since generally it's more useful to look around at the point of the panic than to simulate the kernel running through its panic handling code.
Steve On Fri, Mar 23, 2012 at 7:10 AM, Samuel Hitz <[email protected]> wrote: > Hi there, > > I encounter a > > 9035000: system.cpu.break_event: break event panic triggered > > Now my question is, what could possibly cause such a panic? > I can trace the execution of the program up to the point, where this > happens. Strangely enough, if I just jump past this small part of the > program causing this, the execution can go on. The jumped part does some > writes to memory but it doesn't overwrite code or something. > There is no other relevant output of gem5 before this happens. > > Any help is much appreciated. > > Best, > > Samuel > > _______________________________________________ > 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
