hi there, I am adding this to this thread and not to the trac, because I am not sure whether it adds noise or a piece of info. I just downloaded the scipy trunk and built it, and ran nosetests on it, which bombed instantly.... So I tried to get into subdirs to check test scripts separately..... and here is one :
[co...@jarrett tests]$ ~/.local/bin/ipython test_integrate.py
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)

/home/cohen/sources/python/scipy/scipy/integrate/tests/test_integrate.py in <module>()
    208
    209 if __name__ == "__main__":
--> 210     run_module_suite()
    211
    212

/home/cohen/.local/lib/python2.6/site-packages/numpy/testing/nosetester.pyc in run_module_suite(file_to_run)
     75         f = sys._getframe(1)
     76         file_to_run = f.f_locals.get('__file__', None)
---> 77         assert file_to_run is not None
     78
     79     import_nose().run(argv=['',file_to_run])

AssertionError:
python: Modules/gcmodule.c:277: visit_decref: Assertion `gc->gc.gc_refs != 0' failed.
Aborted (core dumped)
[co...@jarrett tests]$ pwd
/home/cohen/sources/python/scipy/scipy/integrate/tests

the bomb is the same, but the context seems different... I leave that to the experts :)
Johann

On 03/10/2010 06:06 PM, Charles R Harris wrote:


On Wed, Mar 10, 2010 at 10:39 AM, Bruce Southey <bsout...@gmail.com <mailto:bsout...@gmail.com>> wrote:

    On 03/10/2010 08:59 AM, Pauli Virtanen wrote:
    > Wed, 10 Mar 2010 15:40:04 +0100, Johann Cohen-Tanugi wrote:
    >
    >> Pauli, isn't it hopeless to follow the execution of the source
    code when
    >> the crash actually occurs when I exit, and not when I execute.
    I would
    >> have to understand enough of this umath_tests.c.src to spot a
    refcount
    >> error or things like that????
    >>
    > Yeah, it's not easy, and requires knowing how to track this type of
    > errors. I didn't actually mean that you should try do it, just
    posed it
    > as a general challenge to all interested parties :)
    >
    > On a more serious note, maybe there's a compilation flag or
    something in
    > Python that warns when refcounts go negative (or something).
    >
    > Cheers,
    > Pauli
    >
    > _______________________________________________
    > NumPy-Discussion mailing list
    > NumPy-Discussion@scipy.org <mailto:NumPy-Discussion@scipy.org>
    > http://mail.scipy.org/mailman/listinfo/numpy-discussion
    >
    Hi,
    I think I managed to find this. I reverted back my svn versions ($svn
    update -r 8262) and cleaned both the build and installation
    directories.

    It occurred with changeset 8262 (earlier changesets appear okay but
    later ones do not)
    http://projects.scipy.org/numpy/changeset/8262

    Specifically in the file:
    numpy/core/code_generators/generate_ufunc_api.py

    There is an extra call to that should have been deleted on line 54(?).
    Py_DECREF(numpy);

    Attached a patch to ticket 1425
    http://projects.scipy.org/numpy/ticket/1425


Look like my bad. I'm out of town at the moment so someone else needs to apply the patch. That whole bit of code could probably use a daylight audit.

Chuck


--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.


_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Reply via email to