Replies: 2 comments 5 replies
-
|
Looks like we need some extra logic to support the "unavailable" return value for some of the newer registers. Are you using an Intel implementation of gdb that could support pl3_ssp or the default Debian package (which presumably now does not but returns "unavailable" as a place marker)? |
Beta Was this translation helpful? Give feedback.
-
|
Wonderful. So, I acquired the gdb-17.2 source and built it on my system, but I do not see the |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey all,
I'm trying to actively study Ghidra and have run into a roadblock. From following a book, I ran into a weird error. I've gone as far as create a python environment which contains only the built python scripts found in the repo (for version 12.1) and it seems this error still persists whether with the host override whl installs or the virtual environment. I can't seem to find any reports of this online anywhere either, so feels really odd to see this.
The issue is that I'm trying to run the debugger option but get exceptions. I created a breakpoint and went to start a session with gdb + ssh. Due to the constant issues, I have been now trying just gdb in the menu... but still same issues. I should mention, running gdb directly in the terminal on these binaries works perfectly fine. For Ghidra, it throws the following output below into the terminal each time I try to run it. Has anyone else run into this or have suggestions on a fix?
Beta Was this translation helpful? Give feedback.
All reactions