Changeset 2037ec4 for general/prog/gdb.xml
- Timestamp:
- 01/27/2016 11:21:15 PM (8 years ago)
- Branches:
- systemd-13485
- Children:
- 1e76622
- Parents:
- a7e1ac8
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/gdb.xml
ra7e1ac8 r2037ec4 7 7 <!ENTITY gdb-download-http "https://ftp.gnu.org/gnu/gdb/gdb-&gdb-version;.tar.xz"> 8 8 <!ENTITY gdb-download-ftp "ftp://ftp.gnu.org/gnu/gdb/gdb-&gdb-version;.tar.xz"> 9 <!ENTITY gdb-md5sum " 2a35bac41fa8e10bf04f3a0dd7f7f363">9 <!ENTITY gdb-md5sum "39e654460c9cdd80200a29ac020cfe11"> 10 10 <!ENTITY gdb-size "18 MB"> 11 <!ENTITY gdb-buildsize " 580 MB (with the test suite)">12 <!ENTITY gdb-time " 11.4 SBU (with the test suite)">11 <!ENTITY gdb-buildsize "419 MB (additional 349 MB for tests)"> 12 <!ENTITY gdb-time "2.4 SBU (add up to 7.8 SBU for tests)"> 13 13 ]> 14 14 … … 82 82 <xref linkend="doxygen"/>, 83 83 <xref linkend="guile"/>, 84 <xref linkend="python2"/>, and 85 <ulink url="http://sourceware.org/systemtap">SystemTap (optional runtime 86 dependency, also used in a few tests)</ulink>. 84 <xref linkend="python2"/>, 85 <xref linkend="valgrind"/>, and 86 <ulink url="https://sourceware.org/systemtap/">SystemTap</ulink> 87 (run-time dependency, also used in a few tests) 87 88 </para> 88 89 … … 111 112 112 113 <para> 113 To run the test suite, issue the following commands:114 To test the results, issue: 114 115 </para> 115 116 116 117 <screen><userinput>pushd gdb/testsuite && 117 make site.exp&&118 echo "set gdb_test_timeout 120" >>site.exp &&118 make site.exp && 119 echo "set gdb_test_timeout 120" >> site.exp && 119 120 runtest TRANSCRIPT=y 120 121 popd</userinput></screen> 121 122 122 123 <para> 123 There are many problems with the test suite. Your results will depend on 124 installed compilers, as well as whether or not you are running it locally 125 or remotely. Although we do extend the timeout above, there are still many 126 tests that will time out. Note that by changing the timeout value, the 127 number of tests is no longer conserved. There are also failures associated 128 with system readline 6.x among others. Unexpected failures should be about 129 0.5%. 124 See <emphasis>gdb/testsuite/README</emphasis> and <ulink 125 url="https://sourceware.org/gdb/wiki/TestingGDB">TestingGDB</ulink>. 126 There are many problems with the test suite. First one is that you need 127 to clean some directories, if re-running the tests. For that reason, it 128 is recommended to make a copy of the compiled source code directory, 129 before the tests, in case you need to run the tests again. Results depend 130 on installed compilers, there are differences if run locally or remotely, 131 a large number of timeouts (there is a variable that can be set to 132 increase time for timeout, but changing it, apparently the total number 133 of tests is not conserved), there are failures associated with system 134 readline 6.x, between others. A few tests assume that the header file 135 <filename><sys/sdt.h></filename>, part of <ulink 136 url="https://sourceware.org/systemtap/">SystemTap</ulink>, is present. 137 Unexpected failures are less than 0.3%. 130 138 </para> 131 139 … … 164 172 </seg> 165 173 <seg> 166 /usr/include/gdb and 167 /usr/share/gdb 174 /usr/{include,share}/gdb and /usr/share/doc/gdb-&gdb-version; 168 175 </seg> 169 176 </seglistitem>
Note:
See TracChangeset
for help on using the changeset viewer.