bpo-35132: Fixes missing target in gdb pep0393 check.#11848
bpo-35132: Fixes missing target in gdb pep0393 check.#11848lisroach merged 3 commits intopython:masterfrom
Conversation
I bet that it depends on the gdb version, I'm waiting for the reply of the bug reporter: https://bugs.python.org/issue35132#msg335518 |
|
@lisroach: Would you mind to add a NEWS entry? Something like "Fix py-list and py-bt commands of python-gdb.py on gdb7." |
|
Sure thing. Maybe it would be better to wrap it in a try: except, if target() fails we try again without target? |
|
Thanks @lisroach for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
|
GH-12284 is a backport of this pull request to the 3.7 branch. |
(cherry picked from commit 1ceb3a3) Co-authored-by: Lisa Roach <lisaroach14@gmail.com>
|
Thanks @lisroach for the PR 🌮🎉.. I'm working now to backport this PR to: 2.7. |
|
Sorry, @lisroach, I could not cleanly backport this to |
|
Oh, this change is specific to Python 3 and doesn't make sense in Python 2 which doesn't have the "pep393" code. |
|
Thanks @lisroach for the fix ;-) |
https://bugs.python.org/issue35132
It looks like it only happens when built with optimizations which means many of the tests don't run, possibly why this was missed.
I believe target() is unneeded here since 'data' would exist regardless of the type of the target. Perhaps @vstinner or @ambv have more insight.
https://bugs.python.org/issue35132