Fix run to instruction checking instruction number vs. trace count

* The trace count could be less than the number of instructions if flow
  control causes some instructions to be skipped (and higher if some
  were repeated!). There's no need to validate this value anyway, RunTo
  will bail when it hits the end of the trace if the number is too high.
This commit is contained in:
baldurk committed 2015-04-01 23:43:08 +01:00
1 parent 05dc259656
commit c049c37b86
1 file changed
+1 -1
+1 -1
View File
@@ -1391,7 +1391,7 @@ namespace renderdocui.Windows
if (int.TryParse(start, out runTo))
{
if (runTo >= 0 && runTo < m_Trace.states.Length)
if (runTo >= 0)
{
RunTo(runTo, true);
break;