[pypy-issue] [issue863] Implement sys._current_frames() for debugging purposes

Armin Rigo tracker at bugs.pypy.org
Tue Sep 6 18:47:12 CEST 2011


Armin Rigo <armin.rigo at gmail.com> added the comment:

Warning: it may not work correctly with the JIT.  We need to think about it. 
The issue is that it gives random other threads access to frames that are
supposedly "private", i.e. that have been "proven" not to escape.  I'm unsure
that calling f.mark_as_escaped() from another thread has the correct effect in
this context.

----------
nosy: +arigo
status: resolved -> chatting

________________________________________
PyPy bug tracker <tracker at bugs.pypy.org>
<https://bugs.pypy.org/issue863>
________________________________________


More information about the pypy-issue mailing list