CGREEN-DEBUG(1)

💅 CGREEN-DEBUG 💅

okay so bestie, welcome to the cgreen-debug manual page — it lives in the General Commands Manual, and it's here to hold your hand while you go bug-hunting in your test suite. no cap, this one's a lifesaver. 🫶

✨ NAME ✨

cgreen-debug — kick off cgreen-runner under a debugger and slam a breakpoint right on a specific test. like, that test. the one that's been ghosting you. 😭

🌸 SYNOPSIS 🌸

cgreen-debug [OPTION...]  LIBRARY TEST

🦋 DESCRIPTION 🦋

cgreen-debug is a script, bestie — a little script with big main character energy. what it does is start up cgreen-runner under a debugger (primarily gdb, iykyk), load a LIBRARY, and break on a named TEST. it's giving "personalized VIP entrance for one specific test". 👑

so, the deets:

• LIBRARY — this is a filename of the shared library that holds your Cgreen tests. usually it's a .so, a .dll, or a .dylib, depending on whatever platform you're living on. no judgement, we love all platforms here. 🌈
• TEST — the name of a test inside that library, and it's gotta be in the format <context>:<test_name>. yes, with the colon. don't forget the colon, that's the whole vibe check. ✨

💖 OPTIONS 💖

• -h, --help — prints some usage info and then dips out. exit stage left. 👋
• -d, --debugger debugger — instead of the default (gdb), use debugger as your debugger. the allowed values are "gdb", "cgdb", and "lldb". pick your fighter. 🥊

👀 SEE ALSO 👀

• cgreen(5)
• cgreen-runner(1)

the full documentation for cgreen-debug and the Cgreen framework lives in the Cgreen manual, available over on GitHub. go read it, it's iconic. 📚✨

fr fr, that's the whole page. go set that breakpoint, bestie. you got this. 💅

mwah 💋 — that was CGREEN-DEBUG(1) from the General Commands Manual, signing off. periodt.