[3.6] bpo-32962: Backport python-gdb.py and test_gdb.py from master (GH-7710) by vstinner · Pull Request #7711 · python/cpython (original) (raw)
- bpo-32962: python-gdb catchs ValueError on read_var() (bpo-32962: python-gdb catchs ValueError on read_var() #7692)
python-gdb now catchs ValueError on read_var(): when Python has no
debug symbols for example.
(cherry picked from commit 019d33b)
- bpo-32962: python-gdb catchs UnicodeDecodeError (bpo-32962: python-gdb catchs UnicodeDecodeError #7693)
python-gdb now catchs UnicodeDecodeError exceptions when calling
string().
(cherry picked from commit d22fc0b)
- bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 (bpo-32962: Fix test_gdb failure in debug build with -mcet -fcf-protection -O0 #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 9b7c74c)
(cherry picked from commit ca4cb84)