]> granicus.if.org Git - python/commit
[3.7] bpo-32962: Backport python-gdb.py and test_gdb.py from master (GH-7710)
authorVictor Stinner <vstinner@redhat.com>
Fri, 15 Jun 2018 17:11:45 +0000 (19:11 +0200)
committerGitHub <noreply@github.com>
Fri, 15 Jun 2018 17:11:45 +0000 (19:11 +0200)
commitca4cb8492c643d1fcac2c5b749595ad5377673ab
treea2f098226f667d88ab3d92eb2e5389f4113416ce
parent9363235467f1321e5bd81f279bfe4bd23d5c8ff6
[3.7] bpo-32962: Backport python-gdb.py and test_gdb.py from master (GH-7710)

* bpo-32962: python-gdb catchs ValueError on read_var() (GH-7692)

python-gdb now catchs ValueError on read_var(): when Python has no
debug symbols for example.

(cherry picked from commit 019d33b7a447e78057842332fb5d3bad01922122)

* bpo-32962: python-gdb catchs UnicodeDecodeError (GH-7693)

python-gdb now catchs UnicodeDecodeError exceptions when calling
string().

(cherry picked from commit d22fc0bc7de7882da204abe50884bbde2da4f9e7)

* bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 (GH-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.

(cherry picked from commit 9b7c74ca32d1bec7128d550a9ab1b2ddc7046287)
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]
Misc/NEWS.d/next/Tools-Demos/2018-06-14-16-16-53.bpo-32962.2YfdwI.rst [new file with mode: 0644]
Misc/NEWS.d/next/Tools-Demos/2018-06-14-16-23-07.bpo-32962.Q3Dwns.rst [new file with mode: 0644]
Tools/gdb/libpython.py