Ignore:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • general/prog/valgrind.xml

    r141ee0a5 r3f2db3a6  
    77  <!ENTITY valgrind-download-http "https://sourceware.org/pub/valgrind/valgrind-&valgrind-version;.tar.bz2">
    88  <!ENTITY valgrind-download-ftp  "ftp://sourceware.org/pub/valgrind/valgrind-&valgrind-version;.tar.bz2">
    9   <!ENTITY valgrind-md5sum        "de56a5532b0c81781db677ca712c585a">
    10   <!ENTITY valgrind-size          "15 MB">
    11   <!ENTITY valgrind-buildsize     "550 MB (add 62 MB for tests)">
    12   <!ENTITY valgrind-time          "0.5 SBU (Using parallelism=4; add 7.5 SBU for tests)">
     9  <!ENTITY valgrind-md5sum        "e3ca8e03c6c527e80e7da5135a1b6beb">
     10  <!ENTITY valgrind-size          "16 MB">
     11  <!ENTITY valgrind-buildsize     "381 MB (add 66 MB for tests)">
     12  <!ENTITY valgrind-time          "0.5 SBU (Using parallelism=4; add 8.1 SBU for tests)">
    1313]>
    1414
     
    1616  <?dbhtml filename="valgrind.html"?>
    1717
    18   <sect1info>
    19     <date>$Date$</date>
    20   </sect1info>
    2118
    2219  <title>Valgrind-&valgrind-version;</title>
     
    3734    </para>
    3835
    39     &lfs110a_checked;
     36    &lfs112_checked;
    4037
    4138    <bridgehead renderas="sect3">Package Information</bridgehead>
     
    106103  <sect2 role="installation">
    107104    <title>Installation of Valgrind</title>
    108 
    109 <!-- Not needed anymore with 3.18.1
     105<!--
    110106    <para>
    111107      First, make several changes that are required for Valgrind to function on
    112       systems with glibc-2.34 installed:
     108      systems with glibc-2.35 installed:
    113109    </para>
    114110
     
    130126      To test the results, issue: <command>make regtest</command>. The tests
    131127      may hang forever if <xref linkend="gdb"/> is not installed. Some tests
    132       are known to hang also, depending on the version of glibc. A few test
    133        can fail in various suites. Problematic
     128      are known to hang also, depending on the version of glibc. A few tests
     129      can fail in various suites. Problematic
    134130      tests can be disabled by changing the <userinput>prereq:</userinput> line
    135131      in the corresponding <filename>.vgtest</filename> file to
     
    139135<screen role="nodump"><userinput>sed -e 's@prereq:.*@prereq: false@' \
    140136    -i {helgrind,drd}/tests/pth_cond_destroy_busy.vgtest</userinput></screen>
     137
     138    <!-- 731 tests, 6 stderr failures, 0 stdout failures, 1 stderrB failure,
     139         0 stdoutB failures, 1 post failure -bdubbs Apr 13. 22
     140         valgrind-3.19.0
     141
     142         732 tests, 4 stderr failures, 0 stdout failures, 1 stderrB failure,
     143         0 stdoutB failures, 1 post failure - bdubbs Oct 26, 22
     144           gdbserver_tests/hginfo                   (stderrB)
     145           memcheck/tests/cdebug_zlib_gnu           (stderr)
     146           memcheck/tests/overlap                   (stderr)
     147           helgrind/tests/tls_threads               (stderr)
     148           drd/tests/pth_mutex_signal               (stderr) -->
    141149
    142150    <note>
Note: See TracChangeset for help on using the changeset viewer.