Hi,

Dag Sverre Seljebotn wrote:
> if you feel that this is the wrong time 
> for fixing up those things and that it halts other kinds of development, 
> you "should" be able to simply change the nodes back to ExprNode and 
> have everything go back to a relatively normal, stable state.

I hacked a bit into the other direction and it seems that we're getting
closer. I first got lxml to compile again :) and then raised the crash bar
in its test suite step by step from 5% over 57% to 89%. I'm now stuck with
an extremely weird crash due to a tuple item being NULL on read, while all
places I can see where such a tuple is constructed do the correct INCREF
before writing the item, so it would surely have crashed before if the NULL
item had come from there. It happens on a tuple key in a dictionary that is
stored in an attribute of an ext-type, so it's actually not the best place
to trace value changes (and yes, I tried disabling the iter-dict transform,
but that didn't fix it).

I'll stop for tonight, but any ideas on this will be warmly appreciated.

Stefan
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to