-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
bpo-35132: Fixes missing target in gdb pep0393 check. #11848
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? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. You can merge it @lisroach, but this fix will need a backport to 3.7.
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