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
[Bug] Wrong python Versione #930
Comments
Sorry, but I don't understand your issue. You didn't provide enough information and you did not follow the Issue Template. We have no idea how you installed GEF and what version you're using ( Also provide us with as much information as possible about the specific error you're encountering, including all displayed error messages. When you say something like "wrong python version": Are you sure that you're using GDB with python-support? |
any updates on this issue? |
anyway to restore the gdb to it's working state.
|
The python version you have compiled with gdb is too old, doesn't support f-string. Run $ gdb -nx -ex 'pi sys.version' -ex quit And post the result here. |
@hugsy result :
|
As I suspected, your version is too old for both Python (3.5.2) and GDB (7). Install or compile a newer version. See https://hugsy.github.io/gef/install/ |
thanks for the help @hugsy |
GEF+GDB version
Operating System
Linux
Describe the issue you encountered
#gdb-gef
File "~/gef/gef.py", line 111
latest_gef_data = http_get(f"https://raw.githubusercontent.com/hugsy/gef/{ver}/scripts/gef.sh")
^
SyntaxError: invalid syntax
The python version is wrong.
I tried to remove all python versions (2.7 and 3.5) and manually installed python3.9.
but the error still remains.
Sorry, this is my first post on github.
Do you read the docs and look at previously closed issues/PRs for similar cases?
No
Architecture impacted
Describe your issue. Without a proper reproduction step-by-step, your issue will be ignored.
Provide a step-by-step to reproduce your issue.
Minimalist test case
Use this field for a minimal code to compile and spot the issue:
You can also provide a Dockerfile if you prefer
Additional context?
The text was updated successfully, but these errors were encountered: