63bcfc2b0e
This doesn't make profiling useful in any way, but it does get things to the point where I can actually open a capture file. And it would be nice if we could progress to the point of loading capture files (with correct data in-tact) and this helps us move down that path. To really do that correctly, we should make some of the widgetry disabled when it isn't useful. We also need to ensure that we add extra decoding information to capture files during shutdown so that any platform can read it back. This would also help the situation of running and reading on separate architectures.
Sysprof is a sampling profiler that uses a kernel module to generate stacktraces which are then interpreted by the userspace program "sysprof".
See the Sysprof homepage for more information.
Questions, patches and bug reports should be sent to the sysprof mailing list sysprof-list@gnome.org.
The list is archived in https://mail.gnome.org/archives/sysprof-list/.
Debugging symbols
The programs and libraries you want to profile should be compiled
with -fno-omit-frame-pointer and have debugging symbols available,
or you won't get much usable information.
Building Sysprof
You need some packages installed. The package names may vary depending on your distribution, the following command works on Fedora 25:
sudo dnf install gcc gcc-c++ ninja-build gtk3-devel
Then do the following:
meson --prefix=/usr build
cd build
ninja
sudo ninja install
WARNING: ninja install will mostly install under the configured install
prefix but installs systemd service configuration directly in the system
default location /usr/lib/systemd so it won't work without root privileges,
even if the install prefix is a user-owned directory.