aboutsummaryrefslogtreecommitdiff
path: root/opcodes/ppc-dis.c
diff options
context:
space:
mode:
authorCarl Love <cel@us.ibm.com>2021-07-22 13:33:59 -0500
committerCarl Love <cel@us.ibm.com>2021-08-12 13:03:19 -0500
commit65f82b1972cca3476b3ef6abf1d9923d34f5d4f5 (patch)
treec46e5d5196cbd3703058f238b8fb11fbf4d51453 /opcodes/ppc-dis.c
parentb2ee4824b177a359c2db590a9978418211435011 (diff)
downloadgdb-65f82b1972cca3476b3ef6abf1d9923d34f5d4f5.zip
gdb-65f82b1972cca3476b3ef6abf1d9923d34f5d4f5.tar.gz
gdb-65f82b1972cca3476b3ef6abf1d9923d34f5d4f5.tar.bz2
Improve forward progress test in python.exp
The test steps into func2 and than does an up to get back to the previous frame. The test checks that the line number you are at after the up command is greater than the line where the function was called from. The assembly/codegen for the powerpc target includes a NOP after the branch-link. func2 (); /* Break at func2 call site. / 10000694: 59 00 00 48 bl 100006ec 10000698: 00 00 00 60 nop return 0; / Break to end. */ 1000069c: 00 00 20 39 li r9,0 The PC at the instruction following the branch-link is 0x10000698 which GDB.find_pc_line() maps to the same line number as the bl instruction. GDB did move past the branch-link location thus making forward progress. The following proposed fix adds an additional PC check to see if forward progress was made. The line test is changed from greater than to greater than or equal.
Diffstat (limited to 'opcodes/ppc-dis.c')
0 files changed, 0 insertions, 0 deletions