Changeset 9ea9aa7 for general/prog/gdb.xml
- Timestamp:
- 04/06/2016 11:23:04 PM (8 years ago)
- Branches:
- systemd-13485
- Children:
- c7facee
- Parents:
- 02d46cb
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/gdb.xml
r02d46cb r9ea9aa7 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 " 39e654460c9cdd80200a29ac020cfe11">9 <!ENTITY gdb-md5sum "b5c784685e1cde65ba135feea86b6d75"> 10 10 <!ENTITY gdb-size "18 MB"> 11 <!ENTITY gdb-buildsize " 419 MB (additional 349 MB for tests)">12 <!ENTITY gdb-time "2. 4 SBU (add up to 7.8SBU for tests)">11 <!ENTITY gdb-buildsize "399 MB (additional 173 MB for tests, additional 1.3 GB for documentation)"> 12 <!ENTITY gdb-time "2.6 SBU (add up to 13 SBU for tests)"> 13 13 ]> 14 14 … … 124 124 See <emphasis>gdb/testsuite/README</emphasis> and <ulink 125 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%. 138 </para> 126 There are many problems with the test suite: 127 </para> 128 129 <itemizedlist> 130 <listitem> 131 <para> 132 Clean directories ire needed if re-running the tests. For that 133 reason, it is recommended to make a copy of the compiled source code 134 directory before the tests in case you need to run the tests again. 135 </para> 136 </listitem> 137 138 <listitem> 139 <para> 140 Results depend on installed compilers. 141 </para> 142 </listitem> 143 144 <listitem> 145 <para> 146 If run remotely over an ssh connection, the tests will hang 147 and require a hard (power cycle) reset of the sytem. 148 </para> 149 </listitem> 150 151 <listitem> 152 <para> 153 There are a large number of timeouts (there is a variable 154 that can be set to increase time for timeout, but 155 changing it will result in a different number of tests being 156 run. 157 </para> 158 </listitem> 159 160 <listitem> 161 <para> 162 There are failures associated with system readline 6.x. 163 </para> 164 </listitem> 165 166 <listitem> 167 <para> 168 A few tests assume that the header file 169 <filename><sys/sdt.h></filename>, part of <ulink 170 url="https://sourceware.org/systemtap/">SystemTap</ulink>, is 171 present. 172 </para> 173 </listitem> 174 175 <listitem> 176 <para> 177 About 3% of the tests fail (out of over 35000 tests). 178 </para> 179 </listitem> 180 181 </itemizedlist> 139 182 140 183 <para>
Note:
See TracChangeset
for help on using the changeset viewer.