pkg.soopen package index

brew / Rang 4884

i386-elf-gdb mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für i386-elf-gdb in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install i386-elf-gdb

local Homebrew formula metadata

Überblick

Paketzusammenfassung

GNU debugger for i386-elf cross development

Befehle und Aliase

  • i386-elf-gdb
  • i386-elf-gdb-add-index
  • i386-elf-gstack

Verlauf

Projektgeschichte und Nutzung

i386-elf-gdb is Homebrew's target-prefixed build of the GNU Debugger for i386-elf cross development. The package matters because it gives bare-metal and operating-system developers a debugger whose executable name matches the target triple used by their cross compiler and binutils.

Projektgeschichte

GDB came from the early GNU system effort. GNU's January 1987 bulletin described GDB as a source-level C debugger written for GNU in 1986, and Richard Stallman's 1986 KTH lecture described it as a symbolic C debugger influenced by DBX.

The Sourceware documentation describes GDB as a debugger for seeing what happens inside a running program or at the moment it crashes, with support for stopping execution, examining state, and changing program behavior. The GDB news archive shows the long public release line, including GDB 4.18 in 1999, the 5.0 release cycle in 2000, and later 6.x releases.

Adoptionsgeschichte

GDB became one of the standard GNU development tools alongside GCC and Binutils. Its adoption spread through Unix-like systems because it could debug native programs, remote targets, and simulator targets, and because GNU toolchains made source-level debugging part of the normal compile-link-debug loop.

The i386-elf-gdb formula is a narrower package-manager artifact: Homebrew labels it as the GNU debugger for i386-elf cross development and ships executables such as i386-elf-gdb. That target prefix is valuable for cross projects because it avoids mixing host debuggers with bare-metal toolchains.

Wie es verwendet wird

Typical use is debugging i386-elf binaries produced by a matching cross compiler, often through a simulator, emulator, remote stub, or kernel-development workflow. The upstream GDB manual's core workflow is unchanged: load a program or symbols, run or connect to a target, set breakpoints, inspect registers and variables, and step through execution.

For package users, the significant detail is the executable prefix. Scripts, Makefiles, and OS-development tutorials can call i386-elf-gdb explicitly and stay separate from /usr/bin/gdb or an unprefixed Homebrew GDB.

Warum Paket-Nerds sich dafür interessieren

This is a classic cross-toolchain package: upstream GDB is broad and old, while the package name encodes the target ABI. Package nerds care because target-prefixed GNU tools make reproducible cross environments possible without replacing the host compiler or debugger.

Zeitleiste

  • 1986: GDB entered distribution as a GNU source-level C debugger.
  • 1987: GNU's bulletin listed GDB among GNU software available from the Free Software Foundation.
  • 1999: GDB 4.18 release announced in the Sourceware news archive.
  • 2000: GDB 5.0 released after a public branch and release cycle.
  • 2026: Homebrew packaged i386-elf-gdb as a GDB build for i386-elf cross development.

Related projects

  • GDB shares the Sourceware binutils-gdb repository with GNU Binutils.
  • It is commonly paired with GCC, GNU Binutils, QEMU, simulators, and remote debugging stubs in cross-development workflows.

Sicherheitslage

Risikostufe: red

escape, surveillance, or offensive capability signal.

Risikoklassifikator

red Risiko · mittel Konfidenz · escape-surveillance-offensive

Warum

  • escape, surveillance, or offensive capability signal

Signale

  • text:debugger

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
i386-elf-gdbExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
i386-elf-gdb-add-indexExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
i386-elf-gstackExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-08-03
Manager-Version17.2
Manager aktualisiert2026-05-10
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:i386-elf-gdb
Version17.2
PaketmanagerHomebrew
Homepagehttps://www.gnu.org/software/gdb/
Zuletzt aktualisiert2026-05-10T20:39:27Z
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated package history
  • pkg.so package database
  • pkgdb category and tag curation