Christian Hergert 37c2a527b4 libsysprof: be more defensive against oddly formed containers
If we get a container file that is in a format we don't quite understand,
avoid crashing and just bail. That will likely result in the inability
to symbolize properly, but better than crashing.

Fixes #100
2023-09-26 17:27:53 -07:00
2023-08-07 15:41:43 -07:00
2022-05-25 14:07:02 -05:00
2023-09-16 09:53:49 +00:00
2023-09-26 20:41:16 +00:00
2016-12-01 02:34:11 -05:00
2016-11-28 14:04:46 -08:00
2016-04-13 05:14:09 -07:00
2016-04-13 05:24:03 -07:00
2016-04-22 18:34:48 -07:00
2023-09-16 16:12:54 -07:00
2023-09-16 16:12:54 -07:00
2022-04-01 16:56:32 -07:00

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.

Merge requests and bug reports should be sent to sysprof's repository on GNOME's GitLab instance. For general discussion and questions, you can create a new topic in GNOME's Discourse.

The former mailing 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 36:

sudo dnf install gcc gcc-c++ ninja-build gtk4-devel libadwaita-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.

Description
Languages
C 98.9%
Meson 1%