#13060: Valgrind complains about glibc 2.15
----------------------------------------------------------------+-----------
Reporter: jpflori |
Owner: tbd
Type: defect |
Status: needs_work
Priority: major |
Milestone: sage-5.1
Component: optional packages |
Resolution:
Keywords: valgrind spkg | Work
issues: testsuite fails
Report Upstream: Fixed upstream, but not in a stable release. |
Reviewers:
Authors: Jean-Pierre Flori | Merged
in:
Dependencies: |
Stopgaps:
----------------------------------------------------------------+-----------
Comment (by jpflori):
On a debian installation on top of recent hardware (corei7-avx) I'm able
to install the old spkg (debian currently ships eglibc 2.13), but get a
SIGILL when launching sage, which comes as no surprise:
https://bugs.kde.org/show_bug.cgi?id=273475
The latest svn version is enough to let sage starts.
On the same install, the test suite with the old spkg yields
{{{
== 599 tests, 77 stderr failures, 56 stdout failures, 0 stderrB failures,
1 stdoutB failure, 3 post failures ==
}}}
the one proposed here yields
{{{
== 599 tests, 77 stderr failures, 56 stdout failures, 0 stderrB failures,
1 stdo
utB failure, 3 post failures ==
}}}
which was expected.
With the latest svn version (you can test it by replace p0 by jp in the
above url):
{{{
== 545 tests, 4 stderr failures, 0 stdout failures, 0 stderrB failures, 1
stdo
utB failure, 0 post failures ==
}}}
On the ubuntu install mentioned above, with the
{{{
== 591 tests, 79 stderr failures, 57 stdout failures, 0 stderrB failures,
0 stdo
utB failure, 3 post failures ==
}}}
and with the latest svn version
{{{
== 534 tests, 4 stderr failures, 1 stdout failures, 0 stderrB failures, 1
stdo
utB failure, 0 post failures ==
}}}
Whatsoever, I'm not sure that the problem of dealing with avx instructions
should be dealt with here.
We surely should wait for a proper release by the valgrind team, the
tested development version is completely arbitrary.
About the test suite failure, I'm not convinced it should prevent
including the updated p0 spkg proposed here, if they were present before.
I must admit I do not remember seeing errors when dealing with #7766, but
we potentially forgot to run the testsuite all along.
If we expect these failures to be fixed, I can definitely not take care of
this with my little knowledge of valgrind.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13060#comment:7>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
