| 1 |
On 05/21/10 - 05:40:38, François Bissey wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> sage-4.4.2 has just been released. I am guessing that Christopher |
| 5 |
> may be preparing for exams in June so I will probably do the bump. |
| 6 |
> I have already bumped sage-doc. |
| 7 |
> |
| 8 |
> Other matters: |
| 9 |
> -The situation on amd64 is still bad. There has been a silent (no |
| 10 |
> revbump) |
| 11 |
> update to cython to deal with a strict-aliasing problem: |
| 12 |
> http://bugs.gentoo.org/show_bug.cgi?id=294585 |
| 13 |
> I don't have the hardware so I cannot check if it has an influence on |
| 14 |
> our |
| 15 |
> problems but it is worth a try. |
| 16 |
> |
| 17 |
|
| 18 |
Just for the record, I've tried sage-4.4.1 and sage-4.4.2 with a |
| 19 |
rebuild of cython and I still have the random "corrupted double-linked |
| 20 |
list" failures on my amd64. Has anyone had any success using valgrind |
| 21 |
to debug this. Is it possible to even use portage valgrind to debug |
| 22 |
Sage? I have 3.5.0 installed, built with FEATURES=splitdebug and Sage |
| 23 |
seems to cleverly avoid all attempts at using it. |
| 24 |
|
| 25 |
Steve |
Archives