# 使用 Homebrew 安装 i386-elf-gdb
查看 i386-elf-gdb 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。
## 安装
```sh
sudo av install brew:i386-elf-gdb
```
其他安装命令:
### macOS
- Homebrew (100%):
```sh
brew install i386-elf-gdb
```
证据: local Homebrew formula metadata
## 软件包事实
- **软件包键:** brew:i386-elf-gdb
- **软件包管理器:** Homebrew
- **版本:** 17.2
- **来源摘要:** GNU debugger for i386-elf cross development
- **主页:**
- **最后更新:** 2026-05-10T20:39:27Z
- **已生成:** 2026-08-03T19:37:03+00:00
## 可执行文件
- i386-elf-gdb (别名)
- i386-elf-gdb-add-index (别名)
- i386-elf-gstack (别名)
## 安装行为
- Bottle: 不可用
## 版本和新鲜度
- 页面生成时间: 2026-08-03
- 管理器版本: 17.2
## 项目历史与用法
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.
### 项目历史
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.
### 采用历史
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.
### 使用方式
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.
### 为什么软件包爱好者会关心
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.
### 时间线
- 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.
### 来源
-
-
-
-
-
-
## 安全说明
escape, surveillance, or offensive capability signal.
- **Geiger 风险:** red / 中
- escape, surveillance, or offensive capability signal
## Combined YAML source
View the package source record on GitHub. [combined/i386-elf-gdb.yml](https://github.com/mxcl/pkgdb/blob/main/combined/i386-elf-gdb.yml)
## 来源
- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph