Show HN: CMusee – C/C++ timeless debugger, record every function called (veefuse.com) 1 points by veexx103 2d ago ↗ HN
[–] veexx103 2d ago ↗ 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 entiretyThis is the minimum memory required to record some projects.curl 6MBflatbuffers 6MBgit 14MBjq 26MBnlohmann/json 18MBraylib 199MBllvm llc 649MBllvm opt 182MBShowcase & Interactive Demo: https://veefuse.com/en/cmusee/playground/curlSome corner cases are not support currently.
[–] szdytom 1d ago ↗ Sorry if I misunderstood, but I think rr(https://rr-project.org/) or Windows TTD can do this too? [–] veexx103 1d ago ↗ No, the key difference is the interact model.The interaction model of rr similar to GDB, but it could navigate back to any point in time.cmusee record all function called, you could browse through them freely, the concept of time was elim.
[–] veexx103 1d ago ↗ No, the key difference is the interact model.The interaction model of rr similar to GDB, but it could navigate back to any point in time.cmusee record all function called, you could browse through them freely, the concept of time was elim.
3 comments
[ 2.3 ms ] story [ 16.3 ms ] threadIt 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.
The interaction model of rr similar to GDB, but it could navigate back to any point in time.
cmusee record all function called, you could browse through them freely, the concept of time was elim.