diff options
| author | Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> | 2018-10-09 15:20:38 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-10-09 15:20:38 (GMT) |
| commit | 25bfb1aa75c8358becdab11142954c8ee9c3607f (patch) | |
| tree | 36b6462db6d32c95f23057b6a39118cea374f9a9 /Python/fileutils.c | |
| parent | 64bcedce8d61e1daa9ff7980cc07988574049b1f (diff) | |
| download | cpython-25bfb1aa75c8358becdab11142954c8ee9c3607f.zip cpython-25bfb1aa75c8358becdab11142954c8ee9c3607f.tar.gz cpython-25bfb1aa75c8358becdab11142954c8ee9c3607f.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)
(cherry picked from commit 79d21331e605fdc941f947621846b8563485aab6)
Co-authored-by: Victor Stinner <vstinner@redhat.com>
Diffstat (limited to 'Python/fileutils.c')
0 files changed, 0 insertions, 0 deletions