50679dba04
Rather than defining them piecemeal in each C and H file, and having problems with headers being included in different orders so that `_POSIX_C_SOURCE` gets a value which is too low, just define the feature test flags in `meson.build`. See `man 7 feature_test_macros`. This is useful for when building sysprof as a subproject beneath a project which doesn’t define these macros, or which targets an older C standard than `gnu11`. Signed-off-by: Philip Withnall <withnall@endlessm.com>
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 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.