maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

[LLDB][MIPS] Fix TestMiExec.py failure. 

Reviewers: ki.stfu, labath

Subscribers: jaydeep, bhushan, lldb-commits, slthakur

Differential Revision: https://reviews.llvm.org/D32340

llvm-svn: 301530
This commit is contained in:
Nitesh Jain 2017-04-27 10:21:46 +00:00
parent 9108ae2b50
commit 93d7ab9d82
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
lldb/packages/Python/lldbsuite/test/tools/lldb-mi/control/TestMiExec.py
View File

@ -319,8 +319,14 @@ class MiExecTestCase(lldbmi_testcase.MiTestCaseBase):
# -exec-step can keep us in the g_MyFunction for gcc # -exec-step can keep us in the g_MyFunction for gcc
self.runCmd("-exec-finish --frame 0") self.runCmd("-exec-finish --frame 0")
self.expect("\^running") self.expect("\^running")
self.expect( it = self.expect(["\*stopped,reason=\"end-stepping-range\".+?main\.cpp\",line=\"30\"",
"\*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 # Test that -exec-step steps into s_MyFunction
# (and that --frame is optional) # (and that --frame is optional)