Hi,
sorry about the lengthy email, but you asked for details :)
windows is certainly out of scope (not even sure if somebody succeeded
compiling libunwind on windows, probably it needs lots of porting).
Some technical details how it now works now (did not finish it yet
completely):
In the PyPy
There was definitely a massive problem with libunwind & JIT frames,
which made it unsuitable for windows and os x
Another issue was that libunwind made traces ten times bigger, for no
immediate benefit other than "it might be useful some day" and added
complexity.
On linux I was getting ~7% of st
Hi,
> Avoiding to make it a hard dependency would be a good idea. Also,
> libunwind is a hack that showed problems when vmprof previously
> supported C frames, and it was removed for that reason. Maybe you
> should give a word about why re-enabling C frames with libunwind looks
> ok now?
Can yo
Hi Richard,
On 15 February 2017 at 11:22, Richard Plangger wrote:
> On my branch (called vmprof-native), libunwind is required to be available
> on the system. Which means that we need to install those on the buildbots
> (which is fine) and libunwind suddenly becomes a dependency when building
>
Hi there,
I'm currently finishing up vmprof native profilng for CPython & PyPy. Here
are some highlights (soon to be released in 0.4.0):
* Native profiling (C stack) is included in the profile (using libunwind)
for Linux & Mac
* Windows 64bit support (no native profiling)
* The platform that read
