Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Pfmon causes a Segmentation Violation(SIGSEGV)?

April 26, 2017causes pfmon segmentation SIGSEGV violation

0

Posted

Pfmon causes a Segmentation Violation(SIGSEGV)?

1 Answer

0

Posted

This can happen either at any invocation or only when running a system wide session. This is known to happen on Debian systems using a libc version of 2.3.1. There is apparently a bug in some version of this package. The libc6.1* package with a version 2.3.1-8 is known to work. • What is the licence of pfmon? Pfmon is using the GNU public licence. See the COPYRIGHT file included in the package. • Does pfmon correlate the samples with the source code? Pfmon-2.0 does not correlate addresses to symbols. Samples contain only numerical values. But pfmon-3.0 does correlation of addresses to symbols with the –resolve-addresses option. The following restrictions do apply: • only kernel addresses are correlated in system-wide mode • correlation is performance in per-process until the measured task does an exec() Correlation applies everywhere there is an address in the samples but is subject to characteristics of the sampling module. For instance, the [compact-ia64] does not correlate no matte