diff options
| author | Victor Stinner <vstinner@redhat.com> | 2018-10-09 14:54:04 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-10-09 14:54:04 (GMT) |
| commit | 79d21331e605fdc941f947621846b8563485aab6 (patch) | |
| tree | 752dc60f09f3bf99e46f75511b652e2fbb54e1c3 /Include/classobject.h | |
| parent | 7b313971805ca9b53f181f7b97e5376d0b89dc06 (diff) | |
| download | cpython-79d21331e605fdc941f947621846b8563485aab6.zip cpython-79d21331e605fdc941f947621846b8563485aab6.tar.gz cpython-79d21331e605fdc941f947621846b8563485aab6.tar.bz2 | |
bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 (GH-9656)
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)
Diffstat (limited to 'Include/classobject.h')
0 files changed, 0 insertions, 0 deletions