Re: [sage-combinat-devel] segfault in 4.8

2012-02-01 Thread Christian Stump
Hi Florent, I don't know if its related, but I got segfault with automorphism group of a graph if the import wasn't in the correct order. It may be completely wrong but I got the impression that Cython isn't catching some mistake like import loops leading to segfault. I'm sorry, I've to run

Re: [sage-combinat-devel] segfault in 4.8

2012-02-01 Thread Nicolas M. Thiery
On Tue, Jan 31, 2012 at 11:54:27PM -0800, Christian Stump wrote: Getting a graph only doesn't seem to be the problem; does the same error occur on other machines as well? Any ideas what the problem might be? I reduced the segfault to: sage: M = matrix(ZZ,3,[0,1,0,-1,0,-1,0,1,0]); M

Re: [sage-combinat-devel] segfault in 4.8

2012-02-01 Thread Nicolas M. Thiery
On Wed, Feb 01, 2012 at 08:14:49PM +0100, Christian Stump wrote: that might be the case, as I do compute the automorphism group somewhere in the code (though I am not quite sure if actually in the constructor for quivers). Do you see a way of solving the problem? See my other e-mail

Re: [sage-combinat-devel] segfault in 4.8

2012-02-01 Thread Florent Hivert
On Wed, Feb 01, 2012 at 08:14:49PM +0100, Christian Stump wrote: Hi Florent, I don't know if its related, but I got segfault with automorphism group of a graph if the import wasn't in the correct order. It may be completely wrong but I got the impression that Cython isn't catching some