bpo-32962: python-gdb catchs UnicodeDecodeError by vstinner · Pull Request #7693 · python/cpython (original) (raw)
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation0 Commits1 Checks0 Files changed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
python-gdb now catchs UnicodeDecodeError exceptions when calling string().
vstinner deleted the python_gdb_unicodedecodeerr branch
vstinner added a commit that referenced this pull request
python-gdb now catchs ValueError on read_var(): when Python has no debug symbols for example.
(cherry picked from commit 019d33b)
python-gdb now catchs UnicodeDecodeError exceptions when calling string().
(cherry picked from commit d22fc0b)
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)
vstinner added a commit that referenced this pull request
… (GH-7711)
python-gdb now catchs ValueError on read_var(): when Python has no debug symbols for example.
(cherry picked from commit 019d33b)
python-gdb now catchs UnicodeDecodeError exceptions when calling string().
(cherry picked from commit d22fc0b)
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)
vstinner added a commit that referenced this pull request
python-gdb now catchs ValueError on read_var(): when Python has no debug symbols for example.
(cherry picked from commit 019d33b)
python-gdb now catchs UnicodeDecodeError exceptions when calling string().
(cherry picked from commit d22fc0b)
bpo-29367: python-gdb.py now supports also method-wrapper (wrapperobject) objects.
(cherry picked from commit 6110833)