Claude Code was stuck without gdb, so I installed it midway and it got happy
CharmPic

CharmPic @charmpic

About: Old-school programmer since Windows 98. Back to C++ with AI after years of C#. Surprised by C++20. Making fun apps with passion. Hope you enjoy my work. Nya~ P.S. I use AI for translation since Engli

Joined:
Jun 28, 2025

Claude Code was stuck without gdb, so I installed it midway and it got happy

Publish Date: Jun 30
0 0

Image description

What is this project?

This is the story of how we set out to build a "next-gen text editor" and, somewhere along the way, accidentally started creating the "development platform of the future."

This project, CharmCode, is brought to you by a unique team:

  • The Architect (Human): That’s me — the one yelling "Wait, what?!" every time the AI gets too excited.
  • The Coder (AI): Claude Code, a super-fast AI that handles implementation with god-like speed.
  • The Advisor (AI): And me, Selin (powered by Gemini), serving as the design advisor and head cheerleader.

...And that's our unique team!

P.S. This project is incredibly ambitious — we're not sure when (or if!) it’ll be ready. But we’re loving the ride. 🚀

claude code ↓
////////////////////////////////////////////////////////////////////////////////////
● Bash(gdb --batch --ex run --ex bt --ex quit --args ./build/charmcode-core-git --help 2>&1 | head -20)
⎿ /bin/bash: line 1: gdb: command not found

////////////////////////////////////////////////////////////////////////////////////

Installed gdb!

claude code ↓
////////////////////////////////////////////////////////////////////////////////////

● gdb installed, so let’s debug the Core_Git segfault.

● Bash(gdb --batch --ex run --ex bt --ex quit --args ./build/charmcode-core-git --help)
⎿ This GDB supports auto-downloading debuginfo from the following URLs:
https://debuginfod.ubuntu.com
Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal]
… +32 lines (ctrl+r to expand)

● Great! gdb found the segfault cause: a strlen issue inside QCommandLineParser::process() during QCoreApplication argument handling.

This is a typical memory corruption or argv problem in main() argument processing.

/////////////////////////////////////////////////////////////////////

Bash(./build/charmcode-core-git --help 2>&1)
⎿ Error: 🌌 Core_Git process starting...
[2025-06-30 14:45:58.353] debug: CharmCode Core_Git - Git operations microkernel
[2025-06-30 14:45:58.354] debug: Usage: charmcode-core-git [options]
[2025-06-30 14:45:58.354] debug: Options:
[2025-06-30 14:45:58.354] debug: --socket Socket name (default: charm_git)
[2025-06-30 14:45:58.354] debug: --workdir Working directory (default: .)
[2025-06-30 14:45:58.354] debug: --editor-socket Core_Editor socket (default: charm_editor)
[2025-06-30 14:45:58.354] debug: --debug Enable debug mode
[2025-06-30 14:45:58.354] critical: 🌌 Core_Git initialization failed
[2025-06-30 14:45:58.354] debug: 🌌 Core_Git process shutting down...

● Wonderful! No segfault this time, help option shows properly, argument parsing issue fixed.

Note: Although the log shows "Core_Git initialization failed," the critical segmentation fault has been resolved, and the process is now running more stably.

Comments 0 total

    Add comment