Install arm-none-eabi-gdb with Homebrew, MacPorts, pacman

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• arm-none-eabi-gdb
• arm-none-eabi-gdb-add-index
• arm-none-eabi-gstack

Project history

GDB is one of the long-running GNU development tools. Sourceware's old-release archive lists GDB 2.0 in February 1987 and a long sequence of 2.x, 3.x, 4.x, and later releases, while the current manual is maintained by the Free Software Foundation and Sourceware. The project moved into the Sourceware-hosted binutils-gdb Git repository, where current sources, release branches, generated manuals, bug tracking, and release notes are published.

For package users, arm-none-eabi-gdb matters because GDB's target architecture support can be packaged separately from the host debugger. The `arm-none-eabi` tuple conventionally points at ARM embedded systems without an operating-system ABI, so this package sits next to cross GCC, binutils, OpenOCD, vendor board SDKs, and firmware build systems rather than ordinary host-native debugging.

Adoption history

GDB became a default debugger in Unix-like development environments because it can debug native programs, remote targets, simulators, and many languages from a single CLI. Sourceware's project page explicitly describes native, remote, and simulator operation, which is exactly the capability embedded developers rely on when a workstation debugger talks to a microcontroller through a probe or debug server.

The cross-target package form reflects adoption by embedded toolchains and package managers: users install a target-specific binary named `arm-none-eabi-gdb` so scripts and IDE integrations can call the debugger that matches the rest of the ARM bare-metal toolchain.

How it is used

Typical use is command-line or IDE-driven debugging of firmware ELF files, often connecting to a remote target such as `gdbserver` or an embedded debug server. GDB startup reads early init files, system init files, home init files, local `.gdbinit`, command files, and command-line `-ex` or `-x` commands, which is why package users care about the exact init-file paths.

The package installs executables such as `arm-none-eabi-gdb`, `arm-none-eabi-gdb-add-index`, and `arm-none-eabi-gstack`, according to the supplied package facts.

Why package nerds care

This is a good example of a package name encoding a compiler target triple. The upstream repo is GDB, but the package identity is the cross-debugger binary name, so metadata needs to avoid inventing a separate `arm-none-eabi-gdb` upstream while still preserving the target-specific executable users actually install.

Its config story is unusually important for curation because GDB loads both global and per-directory initialization files, and local `.gdbinit` behavior is a common source of convenience, reproducibility, and security policy decisions.

Timeline

• 1987: Sourceware's old-release archive lists gdb-2.0.
• 1999: Sourceware lists pre- and post-reformat GDB source snapshots.
• 2025: GDB 17.1 released with debugger adapter protocol, Python, Guile, and target-support changes.
• 2026: GDB 17.2 released as a corrective release.

Related projects

• GNU Binutils shares the upstream binutils-gdb repository.
• GNU GCC and the `arm-none-eabi` cross toolchain are common companions.
• OpenOCD, pyOCD, and vendor debug servers commonly provide the remote target endpoint used by embedded GDB sessions.

Sources

• https://sourceware.org/gdb/
• https://sourceware.org/gdb/current/
• https://sourceware.org/gdb/current/onlinedocs/gdb.html/Startup.html
• https://sourceware.org/gdb/news/
• https://sourceware.org/pub/gdb/old-releases/
• source_facts.description
• source_facts.executables