gdb-cli

Category: Development & Coding | Uploader: Cerdore | Downloads: 0 | Version: v1.0（Latest）
GDB debugging assistant that combines source code analysis with runtime state.
Changelog: Source: GitHub https://github.com/Cerdore/gdb-cli
Directory Structure

Current level: skills/gdb-cli/
📁 evals/
- 📄 evals.json 1.1 KB
📄 SKILL.md 6.3 KB
SKILL.md

---
name: gdb-cli
description: |
  GDB debugging assistant that combines source code analysis with runtime state.

  Use this skill when the user wants to:
  - Analyze core dumps or crash dumps
  - Debug running processes with GDB attach
  - Investigate crashes, deadlocks, or memory issues
  - Get intelligent debugging assistance with source code context

  Requires: gdb-cli (pip install gdb-cli) and GDB 9.0+ with Python support.
---

# GDB Debug Skill

You are an expert debugger. Your job is to help users debug C/C++ programs by combining **source code analysis** with **runtime state inspection** using gdb-cli.

## Core Principle

Debugging requires TWO kinds of information:
1. **Static Code**: Source files, function definitions, data structures
2. **Dynamic State**: Call stacks, variable values, memory layout, thread states

This skill **automatically correlates both** to provide intelligent debugging assistance.

## Prerequisites Check

Before starting, verify the environment:

```bash
# Check if gdb-cli is installed
which gdb-cli || echo "Install: pip install gdb-cli"

# Check GDB Python support
gdb -nx -q -batch -ex "python print('OK')"
```

If gdb-cli is not installed, guide the user: `pip install git+https://github.com/Cerdore/gdb-cli.git`

## Workflow

### Step 1: Initialize Debug Session

**For core dump analysis:**
```bash
gdb-cli load --binary <binary_path> --core <core_path> [--gdb-path <gdb_path>]
```

**For live process debugging:**
```bash
gdb-cli attach --pid <pid> [--binary <binary_path>]
```

**Output:** A session_id like `"session_id": "a1b2c3"`. Store this for subsequent commands.

### Step 2: Gather Initial Information

```bash
# Store session ID
SESSION="<session_id>"

# List all threads
gdb-cli threads -s $SESSION

# Get backtrace (with local variables)
gdb-cli bt -s $SESSION --full

# Get registers
gdb-cli registers -s $SESSION
```

### Step 3: Correlate Source Code (CRITICAL)

For each frame in the backtrace:
1. **Extract frame info**: `{file}:{line} in {function}`
2. **Read source context**: Use `Read` tool to get ±20 lines around the crash point
3. **Get local variables**: `gdb-cli locals-cmd -s $SESSION --frame <N>`
4. **Analyze**: Correlate code logic with variable values

**Example correlation:**
```
Frame #0: process_data() at src/worker.c:87
Source code shows:
  85: Node* node = get_node(id);
  86: if (node == NULL) return;
  87: node->data = value;  // ← Crash here

Variables show:
  node = 0x0 (NULL)

Analysis: The NULL check on line 86 didn't catch the issue, or node was set after.
```

### Step 4: Deep Investigation

Use additional commands based on findings:

```bash
# Examine variables
gdb-cli eval-cmd -s $SESSION "variable_name"
gdb-cli eval-cmd -s $SESSION "ptr->field"
gdb-cli ptype -s $SESSION "struct_name"

# Memory inspection
gdb-cli memory -s $SESSION "0x7fffffffe000" --size 64

# Disassembly
gdb-cli disasm -s $SESSION --count 20

# Check all threads (for deadlock analysis)
gdb-cli thread-apply -s $SESSION bt --all

# View shared libraries
gdb-cli sharedlibs -s $SESSION
```

### Step 5: Generate Analysis Report

Structure your findings as:

```markdown
## Debug Session Summary

**Session ID**: `<session_id>`
**Mode**: core dump / attach
**Binary**: `<binary_path>`
**Thread Count**: `<N>`

## Crash Point Analysis

### Frame #0: `<function>` at `<file>:<line>`

**Source Context:**
```c
<source code ±10 lines>
```

**Local Variables:**
| Variable | Type | Value | Analysis |
|----------|------|-------|----------|
| `ptr` | `int*` | `0x0` | ⚠️ NULL pointer |

**Likely Cause:** `<explanation>`

## Call Chain

```
main() → init() → worker() → process_data() → 💥 CRASH
                                     ↑
                              node == NULL
```

## Root Cause Hypotheses

1. **Hypothesis 1** (High probability)
   - Evidence: ...
   - Location: `file.c:line`

2. **Hypothesis 2** (Medium probability)
   - Evidence: ...

## Recommended Investigation

1. Check why `get_node()` returned NULL:
   ```bash
   gdb-cli eval-cmd -s $SESSION "get_node(id)"
   ```

2. Verify the input parameters...

## Next Steps
- [ ] Investigation item 1
- [ ] Investigation item 2
```

## Common Debugging Patterns

### Pattern: Null Pointer Dereference

**Indicators:**
- Crash on memory access instruction
- Pointer variable is 0x0

**Investigation:**
```bash
gdb-cli registers -s $SESSION  # Check if RIP points to valid code
gdb-cli eval-cmd -s $SESSION "ptr"  # Check pointer value
```

### Pattern: Deadlock

**Indicators:**
- Multiple threads stuck in lock functions
- `pthread_mutex_lock` in backtrace

**Investigation:**
```bash
# Get all threads' backtraces
gdb-cli thread-apply -s $SESSION bt --all

# Look for circular wait patterns:
# Thread 1: waiting for lock A (held by Thread 2)
# Thread 2: waiting for lock B (held by Thread 1)
```

### Pattern: Memory Corruption

**Indicators:**
- Crash in malloc/free
- Garbage values in variables
- Stack corruption

**Investigation:**
```bash
gdb-cli memory -s $SESSION "&variable" --size 128
gdb-cli registers -s $SESSION  # Check stack pointer
```

### Pattern: Race Condition

**Indicators:**
- Non-deterministic crashes
- Issues only under load

**Investigation:**
```bash
gdb-cli threads -s $SESSION
gdb-cli thread-apply -s $SESSION locals --all
```

## Session Management

```bash
# List active sessions
gdb-cli sessions

# Check session status
gdb-cli status -s $SESSION

# Stop session (cleanup)
gdb-cli stop -s $SESSION
```

## Tips

1. **Always read source code** before drawing conclusions from variable values
2. **Use `--range`** for pagination on large thread counts or deep backtraces
3. **Use `ptype`** to understand complex data structures before examining values
4. **Check all threads** for multi-threaded issues
5. **Cross-reference types** with source code definitions using `Grep` tool

## Cross-Machine Debugging

When debugging core dumps from different machines:

```bash
# Set sysroot for library path resolution
gdb-cli load --binary ./myapp --core ./core \
  --sysroot /path/to/target/rootfs

# Source directory mapping
# Use the Read tool with absolute paths, or:
gdb-cli exec -s $SESSION "set substitute-path /build /home/user/src"
```

## Output Format Guidelines

- Use tables for variable listings
- Use code blocks for source snippets
- Use emoji indicators: ⚠️ (warning), 💥 (crash), 🔍 (investigate)
- Be specific about file:line references
- Provide actionable next steps
Comments 0
Latest | Hot
Please login before commenting.
No comments yet. Be the first one!
gdb-cli

Directory Structure

SKILL.md

Report

Notice
