[Numpy-discussion] crash at prompt exit after running test
cohen at lpta.in2p3.fr
Thu Mar 11 15:01:25 EST 2010
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
So I tried to get into subdirs to check test scripts separately..... and
here is one :
[cohen at jarrett tests]$ ~/.local/bin/ipython test_integrate.py
AssertionError Traceback (most recent call last)
209 if __name__ == "__main__":
--> 210 run_module_suite()
75 f = sys._getframe(1)
76 file_to_run = f.f_locals.get('__file__', None)
---> 77 assert file_to_run is not None
python: Modules/gcmodule.c:277: visit_decref: Assertion `gc->gc.gc_refs
!= 0' failed.
Aborted (core dumped)
[cohen at jarrett tests]$ pwd
the bomb is the same, but the context seems different... I leave that to
the experts :)
On 03/10/2010 06:06 PM, Charles R Harris wrote:
> On Wed, Mar 10, 2010 at 10:39 AM, Bruce Southey <bsouthey at gmail.com
> <mailto:bsouthey at 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
> >> 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 at scipy.org <mailto:NumPy-Discussion at scipy.org>
> > http://mail.scipy.org/mailman/listinfo/numpy-discussion
> I think I managed to find this. I reverted back my svn versions ($svn
> update -r 8262) and cleaned both the build and installation
> It occurred with changeset 8262 (earlier changesets appear okay but
> later ones do not)
> Specifically in the file:
> There is an extra call to that should have been deleted on line 54(?).
> Attached a patch to 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.
> 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 at scipy.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion