Show HN: CMusee – C/C++ timeless debugger
I have been working on this alone for 6 years. cmusee is not a step debugger like GDB. It records every function call and assignment statement, and then present it entirety This is the minimum memory required to record some projects. curl 6MB flatbuffers 6MB git 14MB jq 26MB nlohmann/json 18MB raylib 199MB llvm llc 649MB llvm opt 182MB Showcase & Interactive Demo: https://veefuse.com/en/cmusee/playground/curl Some corner cases are not support currently.
Read original source
Source record
Recorded metrics
points · 3 votes
2026-10-30 05:30:28.661Z
cumulative since publication
Research analysis
What changed
Source account: I have been working on this alone for 6 years. cmusee is not a step debugger like GDB. It records every function call and assignment statement, and then present it entirety This is the minimum memory required to record some projects. curl 6MB flatbuffers 6MB git 14MB jq 26MB nlohmann/json 18MB raylib 199MB llvm llc 649MB llvm opt 182MB Showcase & Interactive Demo: https://veefuse.com/en/cmusee/playground/curl Some corner cases are not support currently.
Version & cost evidence
Source votes: 3 votes (Oct 30, 2026 UTC; cumulative since publication); previous same-scope observation: 3 (Oct 29, 2026 UTC). These observations do not establish demand growth.
Who is affected
Identify the existing workflow this change affects before recommending an upgrade. Launch attention does not establish improvement; an API, pricing or availability change may instead create migration work.
Missing comparison points
Missing checks: old versus new behavior, affected plans and regions, availability date, compatibility, rollback path and cost under the same workload.
Migration check
Save the release or policy notice, run the same task on the old and new option, and compare outputs and the full bill. For retirement notices, verify the deadline before scheduling migration.