You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running py-spy record --gil -p somepid --duration 10 --output /tmp/out.svg with py-spy==0.3.2, I'm seeing that the resulting output contains only the filename, but never a leading path.
Here's an example stack that I'm seeing with --format raw:
I would expect the output to be something like handle (gunicorn/workers/ggevent.py:139), where the source of the file is much clearer. The example on the README suggests this should work and this has worked in the past with pyflame.
One possibly related piece of information is that py-spy is being run across containers here.
The text was updated successfully, but these errors were encountered:
garrettheel
changed the title
Output only includes last component of filename
Raw output only includes last component of filename
Feb 7, 2020
benfred
changed the title
Raw output only includes last component of filename
Cross-container output only includes last component of filename
Feb 9, 2020
When profiling from the host os to a program running in a docker container,
we were failling to shorten the filenames appropiately. Fix by using
/proc/PID/root to check if the __init__.py files exist (#220).
When running
py-spy record --gil -p somepid --duration 10 --output /tmp/out.svg
withpy-spy==0.3.2
, I'm seeing that the resulting output contains only the filename, but never a leading path.Here's an example stack that I'm seeing with
--format raw
:I would expect the output to be something like
handle (gunicorn/workers/ggevent.py:139)
, where the source of the file is much clearer. The example on the README suggests this should work and this has worked in the past with pyflame.One possibly related piece of information is that
py-spy
is being run across containers here.The text was updated successfully, but these errors were encountered: