diff options
| author | Carl Love <cel@us.ibm.com> | 2023-03-07 13:34:44 -0600 |
|---|---|---|
| committer | Carl Love <cel@us.ibm.com> | 2023-03-08 11:14:18 -0500 |
| commit | 5992fb8541f1c108681468bb48640f0c7dec1709 (patch) | |
| tree | d86468f5e7938b3b195d176f9542c60258d58fb2 /gdb/python | |
| parent | 9a534b9f8e3d0f3cdb5a20f19ff165693fbb84d2 (diff) | |
| download | binutils-5992fb8541f1c108681468bb48640f0c7dec1709.zip binutils-5992fb8541f1c108681468bb48640f0c7dec1709.tar.gz binutils-5992fb8541f1c108681468bb48640f0c7dec1709.tar.bz2 | |
PowerPC, fix test gdb.arch/altivec-regs.exp
The test fails on Power 10 with the RHEL9 distro. It also fails on
Power 9.
The test set a the breakpoint in main that stops at line:
a = 9; /* start here */. The test then sets a break point at the same
line where it wants to start the test and does a continue. GDB does not
stop again on the same line where it is stopped, but rather continues to
the end of the program.
Initialize variable A to zero so the break on main will stop before setting
a break point on line a = 9; /* start here */.
Make the match on the breakpoint number generic.
Patch has been tested on Power 10 with RHEL 9, Power 10 with Ubuntu 22.04,
and Power 9 with Fedora 36 with no regression failures.
Diffstat (limited to 'gdb/python')
0 files changed, 0 insertions, 0 deletions