Hi, On Friday 21 May 2010 22:55:03 Steven Trogdon wrote: > On 05/21/10 - 05:40:38, François Bissey wrote: > > Hi all, > > > > sage-4.4.2 has just been released. I am guessing that Christopher > > may be preparing for exams in June so I will probably do the bump. > > I have already bumped sage-doc. > > > > Other matters: > > -The situation on amd64 is still bad. There has been a silent (no > > revbump) > > update to cython to deal with a strict-aliasing problem: > > http://bugs.gentoo.org/show_bug.cgi?id=294585 > > I don't have the hardware so I cannot check if it has an influence on > > our > > problems but it is worth a try. > > Just for the record, I've tried sage-4.4.1 and sage-4.4.2 with a > rebuild of cython and I still have the random "corrupted double-linked > list" failures on my amd64. Has anyone had any success using valgrind > to debug this. Is it possible to even use portage valgrind to debug > Sage? I have 3.5.0 installed, built with FEATURES=splitdebug and Sage > seems to cleverly avoid all attempts at using it.
I think you already saw this thread (if not this is what you are looking for): http://groups.google.com/group/sage- devel/browse_thread/thread/cd8005be927fc896 To use valgrind on amd64 follow these steps: - emerge valgrind-3.5.0 (previous versions did not work) - valgrind prints out a message to reinstall libc (or was it glibc ?) with FEATURES=splitdebug - thats defintely needed - edit sage-valgrind in Sage's local/bin directory: remove "-- suppressions=..." option or point to this file (see thread above) and add -- trace-children=yes - start sage with "sage -valgrind" > > Steve Christopher
