Diving into a CAD library with call tree analysis, Part 2
· computer · occtPreviously, I showed how you can study which functions call what in a library by using gdb catchpoints to observe a running process’ call stack every time a syscall is made in the application. That was useful to understand the parts of the program related to external libraries, graphics, multi-threading, and compiler optimization, but it didn’t provide any insight into the mathematical and algorithmic core of the library which generally doesn’t do any syscalls. Here I’ll be showing how you can do this with the tool callgrind. Read more...