retrieving full strack traces from running instances

[dmk23]

I've set up the py-tracebacker option but seeing that it only produces the list of threads without detailed stack traces. Is this intended behavior or I am missing something? In most cases just having the top call from the stack is not very useful to figure out what is really happening.

Yes, I see a way to do this on TipsAndTricks page, but wonder if there is any easily pre-packaged way.

P.S. It might be especially helpful to be able to extract the stack with full context / locals of each call, as done by Django Debug Toolbar. I want to see if anything like that is available before deciding if / how / when we might want to roll our own...

[unbit]

Tracebacker spit out something only when there is something going on on that precise timestep. A non busy uWSGI worker will show nothing.

If you want to track the whole activity continuously, "--profiler pycall" will do a better job.

Eventually we can start thinking about an alternative tracebacker that polls continuously

[xrmx]

I think we can close this.