[Numpy-discussion] Problem with numpy.linalg.eig?

[Geoffrey Zhu]

On Nov 12, 2007 10:26 PM, David Cournapeau <david at ar.media.kyoto-u.ac.jp> wrote:
> Geoffrey Zhu wrote:
> > On Nov 12, 2007 12:37 PM, Keith Goodman <kwgoodman at gmail.com> wrote:
> >> On Nov 12, 2007 10:10 AM, Peter Creasey <p.e.creasey.00 at googlemail.com> wrote:
> >>> The following code calling numpy v1.0.4 fails to terminate on my machine,
> >>> which was not the case with v1.0.3.1
> >>>
> >>>     from numpy import arange, float64
> >>>     from numpy.linalg import eig
> >>>     a = arange(13*13, dtype = float64)
> >>>     a.shape = (13,13)
> >>>     a = a%17
> >>>     eig(a)
> >> It sounds like the same problem that was reported in this thread:
> >>
> >> http://thread.gmane.org/gmane.comp.python.numeric.general/17456/focus=17465
> >
> > The code hangs on my machine too. In the thread you mentioned above, I
> > wrote that using the EGG instead of MSI appears to fix the
> > numpy.test() problem, but maybe it just somehow hides it.
> When you use the MSI, can you always reproduce the problem ? As I said
> previously, it is hard to know for sure without being able to reproduce
> the bug on our own workstation, but if this is a problem between fortran
> and C argument passing, then the result can be pretty random since the
> problem reduced to a pointer pointing at a wrong address (crash, wrong
> value, etc...).
>
> cheers,
>
> David
>
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion at scipy.org
> http://projects.scipy.org/mailman/listinfo/numpy-discussion
>

Yes, with the MSI I can always reproduce the problem with
numpy.test(). It always hangs.With the egg it does not hang. Pointer
problems are usually random, but not random if we are using the same
binaries in EGG and MSI and variables are always initialized to
certain value.