You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cannot run `version` as `GEF` fails to run because of the bug.
GDB is `GNU gdb (Debian 8.3.1-1) 8.3.1`
GEF is AFAIK latest as of writing, just downloaded from https://gef.blah.cat/py
System version of Python 3 is 3.7.5
Operating System
Kali GNU/Linux Rolling Release 2019.4
Describe the issue you encountered
Hello, I attempted to install and use GEF, with GDB and Python versions matching stated requirements.
However, GEF crashes at startup of GDB and GDB remains vanilla.
The error is a Python SyntaxError: invalid syntax. The culprit line* is using the = specifier for f-strings, which was only added in Python 3.8.
Suggested fix is rewriting the culprit line in a retro-compatible manner, e.g. dbg(f"Loading extra plugins from directory={directory}") ; or changing the Minimum Supported Python Version to 3.8.
N.B: There is a second culprit line (2 culprit expressions) which crashes upon fixing the first one:
GEF+GDB version
Operating System
Kali GNU/Linux Rolling Release 2019.4
Describe the issue you encountered
Hello, I attempted to install and use GEF, with GDB and Python versions matching stated requirements.
However, GEF crashes at startup of GDB and GDB remains vanilla.
The error is a Python
SyntaxError: invalid syntax
. The culprit line* is using the=
specifier for f-strings, which was only added in Python 3.8.* I allege it is
gef/gef.py
Line 9826 in 8031fda
Suggested fix is rewriting the culprit line in a retro-compatible manner, e.g.
dbg(f"Loading extra plugins from directory={directory}")
; or changing the Minimum Supported Python Version to 3.8.N.B: There is a second culprit line (2 culprit expressions) which crashes upon fixing the first one:
gef/gef.py
Line 11009 in 8031fda
Fixing that one as well, it appears GEF starts without issue. I suspect there are no more other issues as the whole file would be parsed at startup.
Do you read the docs and look at previously closed issues/PRs for similar cases?
Yes
Architecture impacted
Describe your issue. Without a proper reproduction step-by-step, your issue will be ignored.
gdb -q
Minimalist test case
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered: