Use target remote for remote connections

.github/tests/setup-dockerfile.sh

@@ -11,7 +11,7 @@ RUN if [ -f /etc/debian_version ]; then \
   export DEBIAN_FRONTEND=noninteractive NEEDRESTART_MODE=n && \
   apt-get update && \
   apt-get install -y gdb-multiarch python3-dev python3-pip python3-wheel python3-setuptools \
-    git cmake gcc g++ pkg-config libglib2.0-dev gdbserver qemu-user file; \
+    git cmake gcc g++ pkg-config libglib2.0-dev gdbserver qemu-user file curl wget unzip; \
 fi
 
 # Install python3-full for Ubuntu 24.04
@@ -22,9 +22,10 @@ fi
 # Install dependencies for Fedora-based images
 RUN if [ -f /etc/fedora-release ]; then \
   dnf install -y gdb gdb-gdbserver python3-devel python3-pip python3-wheel python3-setuptools python3-rpm \
-    git cmake gcc gcc-c++ pkg-config glib2-devel qemu-user qemu-user-static file procps-ng && \
+    git cmake gcc gcc-c++ pkg-config glib2-devel qemu-user qemu-user-static file procps-ng wget curl unzip && \
   dnf --enablerepo='*debug*' install -y glibc-debuginfo && \
   dnf clean all; \
+  ln -s /usr/bin/gdb /usr/bin/gdb-multiarch; \
 fi
 
 # Copy only requirements.txt for caching

.github/workflows/coverage.yml

@@ -22,7 +22,7 @@ jobs:
       run: |
         export NEEDRESTART_MODE=n
         sudo apt-get update -qq
-        sudo apt-get install -qq -y gdb-multiarch python3-dev python3-pip python3-wheel python3-setuptools git cmake gcc g++ pkg-config libglib2.0-dev gdbserver qemu-user curl
+        sudo apt-get install -qq -y curl wget gdb-multiarch python3-dev python3-pip python3-wheel python3-setuptools git cmake gcc g++ pkg-config libglib2.0-dev gdbserver qemu-user curl
         sudo apt-get install -y python3-full
 
     - name: Run coverage
@@ -34,8 +34,9 @@ jobs:
         echo PY_VER=`gdb -q -nx -ex "pi print('.'.join(map(str, sys.version_info[:2])))" -ex quit` >> $GITHUB_ENV
         echo GEF_CI_NB_CPU=`grep -c ^processor /proc/cpuinfo` >> $GITHUB_ENV
         echo GEF_CI_ARCH=`uname --processor` >> $GITHUB_ENV
-        python${{ env.PY_VER }} -m pip install --user --upgrade -r tests/requirements.txt --quiet
+        python${{ env.PY_VER }} -m pip install --user --upgrade -r tests/requirements.txt -r docs/requirements.txt  --quiet
         current_score=$(curl --silent https://hugsy.github.io/gef/coverage/gef_py.html | grep pc_cov | sed 's?.*<span class="pc_cov">\([^%]*\)%</span>?\1?g')
+        make -C tests/binaries
         bash scripts/generate-coverage-docs.sh
         new_score=$(cat docs/coverage/gef_py.html | grep pc_cov | sed 's?.*<span class="pc_cov">\([^%]*\)%</span>?\1?g')
         score_diff=$(python -c "print(f'{${new_score} - ${current_score}:.04f}')")

.gitignore

@@ -15,3 +15,5 @@ htmlcov
 .benchmarks
 site/
 untracked/
+.zed/
+Dockerfile

LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2013-2025 crazy rabbidz
+Copyright (c) 2013-65 crazy rabbidz
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

docs/commands/gef-remote.md

@@ -1,15 +1,8 @@
 ## Command `gef-remote`
 
-[`target remote`](https://sourceware.org/gdb/onlinedocs/gdb/Remote-Debugging.html#Remote-Debugging)
-is the traditional GDB way of debugging process or system remotely. However this command by itself
-does a limited job (80's bandwidth FTW) to collect more information about the target, making the
-process of debugging more cumbersome. GEF greatly improves that state with the `gef-remote` command.
-
-📝 **Note**: If using GEF, `gef-remote` **must** be your way or debugging remote processes, never
-`target remote`. Maintainers will provide minimal support or help if you decide to use the
-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]
+> `gef-remote` is deprecated since 2026.04 in favor of `target remote`.
+> The command will be removed in a future release. Do not rely on it.
 
 `gef-remote` can function in 2 ways:
 

docs/compat.md

@@ -2,9 +2,9 @@
 
 This matrix indicates the version of Python and/or GDB
 
-| GEF version | GDB Python compatibility | Python compatibility |
-| :--: | :--: | :--: |
-| [2018.02](https://github.com/hugsy/gef/releases/tag/2018.02) | 7.2 | Python 2.7, Python 3.4+ |
-| [2020.03](https://github.com/hugsy/gef/releases/tag/2020.03) | 7.4 | Python 2.7, Python 3.4+ |
-| [2022.01](https://github.com/hugsy/gef/releases/tag/2022.01) | 8.0 | Python 3.6+ |
-| [2025.01](https://github.com/hugsy/gef/releases/tag/2025.01) | 10.0 | Python 3.10+ |
+|                         GEF version                          | GDB Python compatibility |  Python compatibility   |
+| :----------------------------------------------------------: | :----------------------: | :---------------------: |
+| [2018.02](https://github.com/hugsy/gef/releases/tag/2018.02) |           7.2            | Python 2.7, Python 3.4+ |
+| [2020.03](https://github.com/hugsy/gef/releases/tag/2020.03) |           7.4            | Python 2.7, Python 3.4+ |
+| [2022.01](https://github.com/hugsy/gef/releases/tag/2022.01) |           8.0            |       Python 3.6+       |
+| [2025.01](https://github.com/hugsy/gef/releases/tag/2025.01) |           10.0           |      Python 3.10+       |