[HN Gopher] Trace your Python process line by line with minimal ...
___________________________________________________________________
Trace your Python process line by line with minimal overhead
Author : fywvzqhvnn
Score : 28 points
Date : 2023-01-15 20:56 UTC (2 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| andrewstuart wrote:
| Looks interesting I will definitely try this.
|
| For those that find this interesting, you might also like
| pysnooper - I use it all the time.
|
| https://github.com/cool-RR/PySnooper
|
| https://python.plainenglish.io/pysnooper-stop-debugging-pyth...
| gkbrk wrote:
| Any advantages/disadvantages compared to py-spy [1]?
|
| [1]: https://github.com/benfred/py-spy
| love2read wrote:
| Does something similar exist for nodejs and java?
| Waterluvian wrote:
| A problem I have with Python tracing is Django-specific: often my
| trace is a ton of Django internal code and doesn't even point to
| my code that's causing the problem.
|
| Not sure if there's a way to address this kind of issue. Or if
| it's common elsewhere? Just this experience of "what I wrote is
| being run in the context of some library internals and so it
| spits out the internals."
| scrollaway wrote:
| If you're using django, try Sentry. It's good at sorting out
| the noise from the signal, including separating parts of traces
| that aren't relevant to your app.
| loeg wrote:
| USDTs have significant overhead per active probe. I would not
| call that minimal. They are very cheap when inactive, but
| inactive probes can't do this.
___________________________________________________________________
(page generated 2023-01-15 23:00 UTC)