Hello Jaap, I assume you care about the following (computed on sage.math):
sage: dance(11) h^11 - 44*h^10 + 1045*h^9 - 16500*h^8 + 187935*h^7 - 1595748*h^6 + 10199343*h^5 - 48691500*h^4 + 169140180*h^3 - 405230320*h^2 + 600311624*h - 415232800 I am currently computing dance(12) on sage.math. William: feel free to kill pid 5655 in case you consider this a waste of your resources. I had to kill the valgrind process on my local box because valgrind stopped counting errors after the 1,000,000th. I also extrapolated how long it would take and I am not willing to wait a month for it to finish (if it does at all). I started looking at the code itself to see if we cannot come up with an easier to run test case that segfaults and currently I am looking at the components like permanent() and so on that are using via rook_vector. So if you have any ideas where that code could overflow on 32 bit please let me know. Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
