Re: [Python-Dev] Making the new dtrace support work on OS X

2017-01-13 Thread David Cournapeau
On Fri, Jan 13, 2017 at 9:12 PM, Lukasz Langa wrote: > Looks like function-entry and function-return give you the C-level frame > names for some reason. This was implemented on OS X 10.11 if that makes any > difference. I will look at this in the evening, the laptop I'm on now is > macOS Sierra w

Re: [Python-Dev] Making the new dtrace support work on OS X

2017-01-13 Thread Lukasz Langa
Looks like function-entry and function-return give you the C-level frame names for some reason. This was implemented on OS X 10.11 if that makes any difference. I will look at this in the evening, the laptop I'm on now is macOS Sierra with SIP which cripples dtrace. > On Jan 12, 2017, at 5:08 A

[Python-Dev] Making the new dtrace support work on OS X

2017-01-12 Thread David Cournapeau
Hi, I was excited to see official dtrace support for python 3.6.0 on OS X, but I have not been able to make it work: 1. I built my own python from sources on OS X 10.9, with the --with-dtrace support 2. if I launch `python3.6 -q &` and then `sudo dtrace -l -P python$!`, I get the following outpu