diff options
| author | Carl Love <cel@us.ibm.com> | 2021-10-13 22:32:06 +0000 |
|---|---|---|
| committer | Carl Love <cel@us.ibm.com> | 2021-10-21 10:16:52 -0500 |
| commit | e3e4224e79906a518a1446049de9924a60d05e7c (patch) | |
| tree | 78d511517c0e978d40b9da6bfe0d571e7a64c4f8 /gdb/tui | |
| parent | 4d1795ac4dda0f824eae9fd3f810aeb80a993245 (diff) | |
| download | gdb-e3e4224e79906a518a1446049de9924a60d05e7c.zip gdb-e3e4224e79906a518a1446049de9924a60d05e7c.tar.gz gdb-e3e4224e79906a518a1446049de9924a60d05e7c.tar.bz2 | |
Fix test step-and-next-inline.cc
The test expect the runto_main to stop at the first line of the function.
Depending on the optimization level, gdb may stop in the prolog or after
the prolog at the first line. To ensure the test stops at the first line
of main, have it explicitly stop at a break point on the first line of the
function.
On PowerPC, the test passes when compiled with no optimization but fails
with all levels of optimization due to gdb stopping in the prolog.
Diffstat (limited to 'gdb/tui')
0 files changed, 0 insertions, 0 deletions