]> granicus.if.org Git - python/commit
bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 (#6754)
authorMarcel Plch <gmarcel.plch@gmail.com>
Fri, 15 Jun 2018 15:56:24 +0000 (17:56 +0200)
committerVictor Stinner <vstinner@redhat.com>
Fri, 15 Jun 2018 15:56:24 +0000 (17:56 +0200)
commit9b7c74ca32d1bec7128d550a9ab1b2ddc7046287
treeaac6985467e2b287eb47ab0ba1c04edf433f45fe
parentc1897eda3d47b182977459a1e9fed4b3854a10a0
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.
Lib/test/test_gdb.py
Misc/NEWS.d/next/Tests/2018-05-10-16-59-15.bpo-32962.S-rcIN.rst [new file with mode: 0644]