[SciPy-dev] Another segfault

David M. Cooke cookedm at physics.mcmaster.ca
Fri Mar 3 15:12:30 CST 2006

"Nils Wagner" <nwagner at mecha.uni-stuttgart.de> writes:

> On a 64 bit machine scipy.test(1,10) results in a segfault
> The bt message differs from the bt on a 32 bit machine.
> For what reason ?
> Test whether the lu_solve command segfaults, as reported 
> by NilsUse minimum degree ordering on A'+A.
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 5170)]
> 0x00002aaaae34d787 in zpivotL (jcol=0, u=1, 
> usepr=0x7fffffc62264, perm_r=0xc9c7d0, iperm_r=0xbd8c60,
>      iperm_c=0xdb55c0, pivrow=0x7fffffc62270, Glu=0x0, 
> stat=0xffffffffab80bb68) at zpivotL.c:121
> 121             perm_r[*pivrow] = jcol;

btw, I can reproduce this on my 64-bit machine (grr, can't run
scipy.test() right now because of it).

|David M. Cooke                      http://arbutus.physics.mcmaster.ca/dmc/
|cookedm at physics.mcmaster.ca

More information about the Scipy-dev mailing list