Hello, There is a slight problem with the scope object in closures because it is not initialized to NULL in closure frames, it is instead initialized later by assigning a function argument to it. For the debugger this is a problem when execution of the debuggee is halted before this assignment happens, because there is no way to tell whether closed-over variables are valid or not. For e.g. the listing of local variables this is not a big issue, as this is entirely safe. But for code execution this means the debugger will have the debuggee try to put an invalid pointer in a dict in which the code will be executed, with a near 100% chance of segfaulting the debuggee.
So the question is, could we simply initialize the scope objects to NULL? Cheers, Mark
_______________________________________________ Cython-dev mailing list Cython-dev@codespeak.net http://codespeak.net/mailman/listinfo/cython-dev
