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