tracing: bugfix for enabled memory maps
With the recent updates to record one additional instruction at the trace start, I broke memory-map handling (restrictMemoryAddresses() and restrictInstructionAddresses()). This change repairs this functionality. Change-Id: I0daf9f474d0efe3f8e30a168c0ccc1e993e7ddc6
This commit is contained in:
@ -38,6 +38,10 @@ bool TracingPlugin::run()
|
||||
bool first = true;
|
||||
|
||||
while (true) {
|
||||
if (!first) {
|
||||
ev = simulator.resume();
|
||||
}
|
||||
|
||||
curtime = simulator.getTimerTicks();
|
||||
deltatime = curtime - prevtime;
|
||||
|
||||
@ -127,8 +131,6 @@ bool TracingPlugin::run()
|
||||
if (m_os)
|
||||
*m_os << "[Tracing] SOMETHING IS SERIOUSLY WRONG\n";
|
||||
}
|
||||
|
||||
ev = simulator.resume();
|
||||
}
|
||||
|
||||
return true;
|
||||
|
||||
Reference in New Issue
Block a user