christoph/fail
1
Fork 0
Code Releases Activity

tracing: bugfix for enabled memory maps

Browse Source 
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:
Horst Schirmeier
2013-11-18 15:49:06 +01:00
parent bd91549367
commit 85fffe007e
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/plugins/tracing/TracingPlugin.cc
View File

@ -38,6 +38,10 @@ bool TracingPlugin::run()
bool first = true; bool first = true;
while (true) { while (true) {
if (!first) {
ev = simulator.resume();
}
curtime = simulator.getTimerTicks(); curtime = simulator.getTimerTicks();
deltatime = curtime - prevtime; deltatime = curtime - prevtime;
@ -127,8 +131,6 @@ bool TracingPlugin::run()
if (m_os) if (m_os)
*m_os << "[Tracing] SOMETHING IS SERIOUSLY WRONG\n"; *m_os << "[Tracing] SOMETHING IS SERIOUSLY WRONG\n";
} }
ev = simulator.resume();
} }
return true; return true;