On 4/29/25 12:15, Serhei Makarov wrote:
There is an issue with spontaneous exit of sysprofd (cleanly, with a
"Stopping RAPL monitor" message) that I'm trying to understand.
Oh, and one quick other thing.
I had issues with SELinux killing things while developing. `setenforce
0` "fixed" it. But
On 4/29/25 12:15, Serhei Makarov wrote:
There is an issue with spontaneous exit of sysprofd (cleanly, with a
"Stopping RAPL monitor" message) that I'm trying to understand.
Sysprofd only stays alive as long as it's being used (plus some 30
second timeout or so). So that generally means that so
On 4/15/25 09:12, Serhei Makarov wrote:
Option 2: expose one function, treat file_name and fd as optional input
parameters.
// normal use case
module_name = "/usr/lib/whatever.so"; /* name of module */
file_name = "/proc/PID/root/usr/lib/whatever.so"; /* actual location of module
*/
dwfl_proce
On vacation until 2025 so my replies will be sparse here :)
On 12/11/24 3:24 AM, Milian Wolff wrote:
For symmetry reasons, we also need an `..._end` method. And what about
explicitly removing processes once they have finished (PERF_RECORD_EXIT)?
One area you can run into issues with this is th
On 5/11/23 12:27 PM, Serhei Makarov wrote:
When the sysprof libraries are available, we could also use sysprof's
mount namespace conversion code (in whatever eventual form it takes)
to get .eh_frame data.
Is it correct that we won't get a PERF_EVENT_MMAP2 for all the processes
already running
First off, this all sounds great!
I'm not on the mailing list, so apologies if this takes extra-effort to
show up there.
On 5/8/23 5:33 AM, Serhei Makarov wrote:
eu-stacktrace will be a utility to process a stream of raw stack
samples (such as those obtained from the Linux kernel's
PERF_SAMPL
