Difference between revisions of "Coder Tools"
From GnuCash
(heaptrack) |
(Profiling, from https://lists.gnucash.org/logs/2020/03/04.html#T14:32:01) |
||
| Line 2: | Line 2: | ||
==Memory Leaks== | ==Memory Leaks== | ||
| − | |||
* [https://www.kdab.com/heaptrack-v1-0-0-release/ heaptrack] [https://www.kdab.com/heaptrack-v1-1-0-release/ v1-1-0-release] from [https://code.gnucash.org/logs/2018/09/09.html#T17:00:42] | * [https://www.kdab.com/heaptrack-v1-0-0-release/ heaptrack] [https://www.kdab.com/heaptrack-v1-1-0-release/ v1-1-0-release] from [https://code.gnucash.org/logs/2018/09/09.html#T17:00:42] | ||
[[Category:Development]] | [[Category:Development]] | ||
| + | |||
| + | ==Profiling== | ||
| + | |||
| + | For C exist [https://github.com/GNOME/sysprof sysprof], [https://github.com/KDE/heaptrack heaptrack], [https://en.wikipedia.org/wiki/Valgrind Valgrind],... Plenty of [https://en.wikipedia.org/wiki/List_of_performance_analysis_tools profiling tools]. I'm have done some profiling with sysprof and heaptrack (never used valgrind). Both have interactive user interfaces to drill down on profiling data. I currently prefer heaptrack as it doesn't need special privileges. Last time I used sysprof (which has been a while) it needed admin privileges to run. | ||
Revision as of 20:24, 6 March 2020
Sometimes somebody finds a tool, which is better than standard tools. Here we share our knowledge.
Memory Leaks
- heaptrack v1-1-0-release from [1]
Profiling
For C exist sysprof, heaptrack, Valgrind,... Plenty of profiling tools. I'm have done some profiling with sysprof and heaptrack (never used valgrind). Both have interactive user interfaces to drill down on profiling data. I currently prefer heaptrack as it doesn't need special privileges. Last time I used sysprof (which has been a while) it needed admin privileges to run.
