Conversation
…y/gef into hugsy/revisit-target-remote
Grazfather
left a comment
Grazfather
left a comment
There was a problem hiding this comment.
Seems to work pretty well even with an openocd gdb server. Will have to do more testing but we can probably remove the 'special' gef remote commands in gef-extras
docs/commands/gef-remote.md
Outdated
| traditional `target remote` command. For many reasons, you **should not** use `target remote` alone | ||
| with GEF. It is still important to note that the default `target remote` command has been | ||
| overwritten by a minimal copy `gef-remote`, in order to make most tools relying on this command work. | ||
| 📝 **IMPORTANT NOTE**: `gef-remote` is deprecated since 2024.09 in favor of `target remote`. The |
There was a problem hiding this comment.
I guess it'll be the next release
| # pre-hooks | ||
| gdb.execute(hook.format("remote", "")) | ||
| gdb.execute(hook.format("extended-remote", "")) | ||
| # post-hooks |
There was a problem hiding this comment.
This is probably OK if we update what versions of GDB are supported.
|
when running the following arm program: the main branch works fine with the follwing: but using the gef from this branch is failing: will there be a workaround? |
|
@micsthepick I think you need to provide the |
|
|
4 participants
Description
This PR obsoletes
gef-remoteto be completely replaced by pre and post hooks ontarget remotedirectly.We use some heuristics to determine what type of remote we're connected to reliably.
In some old qemu, we still have to mock a memory layout, but the whole
syncthing is not necessary any longer.Fixes #1080
Fixes #1128
Checklist