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.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
Thanks for catching this! Could you update this CL to let me commit it?
packages/Python/lldbsuite/test/tools/lldb-mi/control/TestMiExec.py | ||
---|---|---|
287–289 | Remove this. | |
306–313 | Please do like this. | |
325–336 | 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. self.runCmd("-exec-step") self.expect("\^running") self.expect( "\*stopped,reason=\"end-stepping-range\".+?main\.cpp\",line=\"30\"") | |
packages/Python/lldbsuite/test/tools/lldb-mi/control/main.cpp | ||
29–30 | Revert this |
lldb/trunk/packages/Python/lldbsuite/test/tools/lldb-mi/control/TestMiExec.py | ||
---|---|---|
329 ↗ | (On Diff #96890) | I mistyped there should be -exec-next,, and why you are not checking that it has stopped at the right line (as I suggested)? |
lldb/trunk/packages/Python/lldbsuite/test/tools/lldb-mi/control/TestMiExec.py | ||
---|---|---|
329 ↗ | (On Diff #96890) | ohh. i just forgot to do that . I will update it |
Remove this.