diff options
| author | Victor Stinner <vstinner@redhat.com> | 2018-10-10 12:54:04 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-10-10 12:54:04 +0200 |
| commit | b274f1ce5c62dd517338b8323fb9eb5aaa09c7cd (patch) | |
| tree | a977ded14e4323245e84e6ca84420de37eaac27b /Misc | |
| parent | 4a7dd30f5810e8861a3834159a222ab32d5c97d0 (diff) | |
| download | cpython-git-b274f1ce5c62dd517338b8323fb9eb5aaa09c7cd.tar.gz | |
bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 (GH-9656) (GH-9788)
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.
test_gdb: get_gdb_repr() now uses the "backtrace 1" command after
breakpoint, as in the master branch.
Co-Authored-By: Marcel Plch <gmarcel.plch@gmail.com>
(cherry picked from commit 9b7c74ca32d1bec7128d550a9ab1b2ddc7046287)
(cherry picked from commit 79d21331e605fdc941f947621846b8563485aab6)
Diffstat (limited to 'Misc')
| -rw-r--r-- | Misc/NEWS.d/next/Tests/2018-05-10-16-59-15.bpo-32962.S-rcIN.rst | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Misc/NEWS.d/next/Tests/2018-05-10-16-59-15.bpo-32962.S-rcIN.rst b/Misc/NEWS.d/next/Tests/2018-05-10-16-59-15.bpo-32962.S-rcIN.rst new file mode 100644 index 0000000000..97328ebafe --- /dev/null +++ b/Misc/NEWS.d/next/Tests/2018-05-10-16-59-15.bpo-32962.S-rcIN.rst @@ -0,0 +1 @@ +Fixed test_gdb when Python is compiled with flags -mcet -fcf-protection -O0. |