| commit | 9b7c74ca32d1bec7128d550a9ab1b2ddc7046287 | [log] [tgz] |
|---|---|---|
| author | Marcel Plch <gmarcel.plch@gmail.com> | Fri Jun 15 17:56:24 2018 +0200 |
| committer | Victor Stinner <vstinner@redhat.com> | Fri Jun 15 17:56:24 2018 +0200 |
| tree | aac6985467e2b287eb47ab0ba1c04edf433f45fe | |
| parent | c1897eda3d47b182977459a1e9fed4b3854a10a0 [diff] |
bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 (#6754) When Python is built with the intel control-flow protection flags, -mcet -fcf-protection, gdb is not able to read the stack without actually jumping inside the function. This means an extra 'next' command is required to make the $pc (program counter) enter the function and make the stack of the function exposed to gdb.