Skip to content

[3.7] bpo-32962: Backport python-gdb.py and test_gdb.py from master #7710

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 and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 15, 2018
Merged

[3.7] bpo-32962: Backport python-gdb.py and test_gdb.py from master #7710

merged 3 commits into from
Jun 15, 2018

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Jun 15, 2018

vstinner and others added 3 commits June 15, 2018 18:26
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)
…tion -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)
@vstinner vstinner changed the title [3.7] Backport python-gdb.py and test_gdb.py from master [3.7] bpo-32962: Backport python-gdb.py and test_gdb.py from master Jun 15, 2018
@vstinner vstinner merged commit ca4cb84 into python:3.7 Jun 15, 2018
@vstinner vstinner deleted the python_gdb37 branch June 15, 2018 17:11
vstinner added a commit that referenced this pull request Jun 15, 2018
… (GH-7711)

* 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 019d33b)

* bpo-32962: python-gdb catchs UnicodeDecodeError (GH-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 (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 9b7c74c)

(cherry picked from commit ca4cb84)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants