message: [LLDB][MIPS] Fix TestMiExec.py failure.
  Reviewers: ki.stfu, labath
  Subscribers: jaydeep, bhushan, lldb-commits, slthakur
diff: @@ -319,8 +319,14 @@ class MiExecTestCase(lldbmi_testcase.MiTestCaseBase):
  # -exec-step can keep us in the g_MyFunction for gcc
  self.runCmd("-exec-finish --frame 0")
  self.expect("\^running")
  - self.expect(
  - "\*stopped,reason=\"end-stepping-range\".+?main\.cpp\",line=\"30\"")
  + it = self.expect(["\*stopped,reason=\"end-stepping-range\".+?main\.cpp\",line=\"30\"",
  + "\*stopped,reason=\"end-stepping-range\".+?main\.cpp\",line=\"29\""])
  +
  + if it == 1:
  + # Call to s_MyFunction may not follow immediately after g_MyFunction.
  + # There might be some instructions in between to restore caller-saved registers.
  + # We need to get past these instructions with a step to reach call to s_MyFunction.
  + self.runCmd("-exec-step --thread 1")
  # Test that -exec-step steps into s_MyFunction
  # (and that --frame is optional)
  