pyflame Kernel version less than 3.4 support

Hi, Thanks for developing pyflame, if it possible to add support on kernel version less than 3.4?

PTRACE_SEIZE/PTRACE_INTERRUPT (since Linux 3.4)

Nov 02 '17 11:11 ssskip

Hi @ssskip,

The original version of Pyflame didn't use PTRACE_SEIZE, seizing was added by commit 143144a9f29eefe832490b703348824dc66160a3 . The last version that did not use PTRACE_SEIZE can be fetched using the git tag v1.5.2. I am going to leave this issue open because I think that Pyflame should be able to work without PTRACE_SEIZE, but in the meantime can you try v1.5.2?

Nov 06 '17 23:11 eklitzke

@eklitzke thanks for your update, so if i use pt_attach version,it’s not possible to do a runtime prof on long running python process,right?

since

Unlike PTRACE_ATTACH, PTRACE_SEIZE does not stop the process.

Nov 07 '17 12:11 ssskip

@eklitzke BTW, I think append kernel version build check can be helpful for people try to compile pyflame on unsupport version.

Nov 07 '17 12:11 ssskip

I believe this can be done as a check in configure.ac using an AC_COMPILE_IFELSE check. Kind of hard for me to test since I don't have any kernels that old. A PR would be welcome.

Mar 19 '18 08:03 eklitzke

This is also a blocker for getting newer version into conda-forge: https://github.com/conda-forge/staged-recipes/pull/6601

Sep 03 '18 07:09 xhochy