Issue64

Title PyThreadState->c_traceobj writeable in nuitka
Priority bug Status chatting
Superseder Nosy List nssh
Assigned To Keywords

Created on 2013-03-11.19:13:00 by nssh, last changed by kayhayen.

Messages
msg224 (view) Author: kayhayen Date: 2013-03-12.13:34:14
If you are compiling a module, it would be OK to ignore it. For a whole program, 
tracing may still be used for those parts not compiled.

It would be nice, if compiled programs output a warning, that explains why so 
little will be seen. Or maybe, just maybe, get it to work with compiled frames, 
although I think if you need tracing, you can just use CPython in that instance 
normally.

Unsure what to do here.
msg208 (view) Author: nssh Date: 2013-03-11.19:13:00
test code:
import sys
def a():
	pass
def trace(*args):
	print args
sys.settrace(trace)
a()

run result:
[test@localhost Nuitka]$ python ../settrace.py 
(<frame object at 0x89af97c>, 'call', None)
[test@localhost Nuitka]$ ./bin/nuitka-python ../settrace.py 
[test@localhost Nuitka]$ 

I think it need raise a runtimeerror at sys.settrace.
sys.settrace will set these property
PyThreadState->c_tracefunc
PyThreadState->c_traceobj
PyThreadState->use_tracing
Anyway this isn't a big problem.
History
Date User Action Args
2013-03-12 13:34:14kayhayensetstatus: unread -> chatting
messages: + msg224
2013-03-11 19:13:00nsshcreate