Staging
v0.5.1
https://github.com/python/cpython
Revision 25bfb1aa75c8358becdab11142954c8ee9c3607f authored by Miss Islington (bot) on 09 October 2018, 15:20:38 UTC, committed by GitHub on 09 October 2018, 15:20:38 UTC

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.

Co-Authored-By: Marcel Plch <gmarcel.plch@gmail.com>

(cherry picked from commit 9b7c74ca32d1bec7128d550a9ab1b2ddc7046287)
(cherry picked from commit 79d21331e605fdc941f947621846b8563485aab6)

Co-authored-by: Victor Stinner <vstinner@redhat.com>
1 parent 64bcedc
History
Tip revision: 25bfb1aa75c8358becdab11142954c8ee9c3607f authored by Miss Islington (bot) on 09 October 2018, 15:20:38 UTC
bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 (GH-9656)
Tip revision: 25bfb1a
File Mode Size
ci.yml -rw-r--r-- 2.7 KB
docker-steps.yml -rw-r--r-- 2.2 KB
docs-steps.yml -rw-r--r-- 1.3 KB
macos-steps.yml -rw-r--r-- 724 bytes
posix-deps.sh -rwxr-xr-x 590 bytes
posix-steps.yml -rw-r--r-- 1.9 KB
pr.yml -rw-r--r-- 1.8 KB
prebuild-checks.yml -rw-r--r-- 1.2 KB
windows-steps.yml -rw-r--r-- 1.1 KB

back to top