4 ms·
There is a lot of profiling and debugging tools for C/C++, funny enough a lot of them are originated from the KDE community. From the top of my mind: * valgrin
by ognarb 5y ago
There is a lot of profiling and debugging tools for C/C++, funny enough a lot of them are originated from the KDE community. From the top of my mind:
* valgrind (https://valgrind.org/ https://valgrind.org/): Contains a lot of tools
* Heaptrack (https://apps.kde.org/heaptrack/ https://apps.kde.org/heaptrack/): For memory allocation analysis
* KCachegrind (https://apps.kde.org/kcachegrind/ https://apps.kde.org/kcachegrind/): For call graph vizualisations
* ELF Dissector (https://apps.kde.org/elf-dissector/ https://apps.kde.org/elf-dissector/): For analysis of binary files/dependencies
* Massif-Visualizer (https://apps.kde.org/massif-visualizer/ https://apps.kde.org/massif-visualizer/): Valgrind massif visualiser
* Gammaray (https://www.kdab.com/development-resources/qt-tools/gammaray/ https://www.kdab.com/development-resources/qt-tools/gammaray...): Tool to analysis the current state of a Qt project a bit like you would do with firefox inspector.
- eitland 5y ago> funny enough a lot of them are originated from the KDE community. How is that funny?
- jraph 5y agoFunny is probably a funny way of saying noteworthy here.
- dralley 5y agoFYI, most of these work great on other languages languages. Massif and most of the valgrind suite (cachegrind, callgrind, memcheck) can be used with Rust.
- ognarb 5y agoYeah I use kcachegrind with xdebug/php for my day job
- The_rationalist 5y agoand most importantly ASAN/MSAN/TSAN/UBSAN. (Although I admit that the inability to use ASAN and MSAN simultaneously is a big limitation that Valgrind doesn't have