On Feb 20, 2009, at 2:45 AM, Robert Bradshaw wrote: > On Feb 20, 2009, at 1:59 AM, Michael Abshoff wrote: > >> Robert Bradshaw wrote: >>> On Feb 20, 2009, at 1:25 AM, Stefan Behnel wrote: >>> >>>> Dag Sverre Seljebotn wrote: >>>>> The solution may be to change the way Cython/Runtime/refnanny.pyx >>>>> reports errors, for instance change Context.delref to do a >>>>> print/sys.exit(1) thing instead of raising an exception >>>> I would prefer a simple sys.__stderr__.write() with some helpful >>>> information in a dedicated code line that you could point gdb to. >>>> Killing >>>> the process sounds everything but helpful. Note that sys.exit() >>>> also just >>>> raises an exception, as opposed to os._exit(). >>> >>> +1. If memory is leaking, I'd rather have it tell me and move on. Of >>> course if there are reference errors later on it may segfault, >>> but at >>> least I'd have useful information already. >> >> Not surprisingly we get bitten by the widely discussed ctypedef >> sizt_t >> thingy: >> >> # Memory management >> cdef extern from "stdlib.h": >> ctypedef unsigned long size_t >> >> >>> - Robert >> >> Before I go off and make a fool of myself fixing various potential >> Cython issues in 3.3.rc2: Robert - do you have a patch or a list of >> known issues? If the above is the only problem I can probably >> handle it :) > > I'll make a 0.11 ticket and post a patch. I got sage to compile, but > it fails to start up.
http://trac.sagemath.org/sage_trac/ticket/4987 _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
