Commit | Line | Data |
---|---|---|
b866c52d SS |
1 | This is a collection of tests for GDB. |
2 | ||
3 | The file gdb/README contains basic instructions on how to run the | |
4 | testsuite, while this file documents additional options and controls | |
5 | that are available. The GDB wiki may also have some pages with ideas | |
6 | and suggestions. | |
7 | ||
8 | ||
9 | Running the Testsuite | |
10 | ********************* | |
11 | ||
12 | There are two ways to run the testsuite and pass additional parameters | |
13 | to DejaGnu. The first is to do `make check' in the main build | |
14 | directory and specifying the makefile variable `RUNTESTFLAGS': | |
15 | ||
16 | make check RUNTESTFLAGS='TRANSCRIPT=y gdb.base/a2-run.exp' | |
17 | ||
18 | The second is to cd to the testsuite directory and invoke the DejaGnu | |
19 | `runtest' command directly. | |
20 | ||
21 | cd testsuite | |
22 | make site.exp | |
23 | runtest TRANSCRIPT=y | |
24 | ||
25 | (The `site.exp' file contains a handful of useful variables like host | |
26 | and target triplets, and pathnames.) | |
27 | ||
e352bf0a PA |
28 | Parallel testing |
29 | **************** | |
30 | ||
31 | If not testing with a remote host (in DejaGnu's sense), you can run | |
32 | the GDB test suite in a fully parallel mode. In this mode, each .exp | |
33 | file runs separately and maybe simultaneously. The test suite ensures | |
34 | that all the temporary files created by the test suite do not clash, | |
35 | by putting them into separate directories. This mode is primarily | |
36 | intended for use by the Makefile. | |
37 | ||
38 | For GNU make, the Makefile tries to run the tests in parallel mode if | |
39 | any -j option is given. For a non-GNU make, tests are not | |
40 | parallelized. | |
41 | ||
42 | If RUNTESTFLAGS is not empty, then by default the tests are | |
43 | serialized. This can be overridden by either using the | |
44 | `check-parallel' target in the Makefile, or by setting FORCE_PARALLEL | |
45 | to any non-empty value: | |
46 | ||
acc23c11 PA |
47 | make check-parallel RUNTESTFLAGS="--target_board=native-gdbserver" |
48 | make check RUNTESTFLAGS="--target_board=native-gdbserver" FORCE_PARALLEL=1 | |
e352bf0a PA |
49 | |
50 | If you want to use runtest directly instead of using the Makefile, see | |
51 | the description of GDB_PARALLEL below. | |
52 | ||
fb6a751f SDJ |
53 | Racy testcases |
54 | ************** | |
55 | ||
56 | Sometimes, new testcases are added to the testsuite that are not | |
57 | entirely deterministic, and can randomly pass or fail. We call them | |
58 | "racy testcases", and they can be bothersome when one is comparing | |
59 | different testsuite runs. In order to help identifying them, it is | |
60 | possible to run the tests several times in a row and ask the testsuite | |
61 | machinery to analyze the results. To do that, you need to specify the | |
62 | RACY_ITER environment variable to make: | |
63 | ||
64 | make check RACY_ITER=5 -j4 | |
65 | ||
66 | The value assigned to RACY_ITER represents the number of times you | |
67 | wish to run the tests in sequence (in the example above, the entire | |
68 | testsuite will be executed 5 times in a row, in parallel). It is also | |
69 | possible to check just a specific test: | |
70 | ||
71 | make check TESTS='gdb.base/default.exp' RACY_ITER=3 | |
72 | ||
73 | One can also decide to call the Makefile rules by hand inside the | |
74 | gdb/testsuite directory, e.g.: | |
75 | ||
76 | make check-paralell-racy -j4 | |
77 | ||
78 | In which case the value of the DEFAULT_RACY_ITER variable (inside | |
79 | gdb/testsuite/Makefile.in) will be used to determine how many | |
80 | iterations will be run. | |
81 | ||
82 | After running the tests, you shall see a file name 'racy.sum' in the | |
83 | gdb/testsuite directory. You can also inspect the generated *.log and | |
84 | *.sum files by looking into the gdb/testsuite/racy_ouputs directory. | |
85 | ||
86 | If you already have *.sum files generated from previous testsuite runs | |
87 | and you would like to analyze them without having to run the testsuite | |
88 | again, you can also use the 'analyze-racy-logs.py' script directly. | |
89 | It is located in the gdb/testsuite/ directory, and it expects a list | |
90 | of two or more *.sum files to be provided as its argument. For | |
91 | example: | |
92 | ||
93 | ./gdb/testsuite/analyze-racy-logs.py testsuite-01/gdb.sum \ | |
94 | testsuite-02/gdb.sum testsuite-03/gdb.sum | |
95 | ||
96 | The script will output its analysis report to the standard output. | |
97 | ||
71c0c615 YQ |
98 | Running the Performance Tests |
99 | ***************************** | |
100 | ||
101 | GDB Testsuite includes performance test cases, which are not run together | |
102 | with other test cases, because performance test cases are slow and need | |
103 | a quiet system. There are two ways to run the performance test cases. | |
104 | The first is to do `make check-perf' in the main build directory: | |
105 | ||
106 | make check-perf RUNTESTFLAGS="solib.exp SOLIB_COUNT=8" | |
107 | ||
108 | The second is to cd to the testsuite directory and invoke the DejaGnu | |
109 | `runtest' command directly. | |
110 | ||
111 | cd testsuite | |
112 | make site.exp | |
113 | runtest GDB_PERFTEST_MODE=both GDB_PERFTEST_TIMEOUT=4000 --directory=gdb.perf solib.exp SOLIB_COUNT=8 | |
114 | ||
115 | Only "compile", "run" and "both" are valid to GDB_PERFTEST_MODE. They | |
116 | stand for "compile tests only", "run tests only", and "compile and run | |
117 | tests" respectively. "both" is the default. GDB_PERFTEST_TIMEOUT | |
118 | specify the timeout, which is 3000 in default. The result of | |
119 | performance test is appended in `testsuite/perftest.log'. | |
120 | ||
b866c52d SS |
121 | Testsuite Parameters |
122 | ******************** | |
123 | ||
124 | The following parameters are DejaGNU variables that you can set to | |
125 | affect the testsuite run globally. | |
126 | ||
127 | TRANSCRIPT | |
128 | ||
129 | You may find it useful to have a transcript of the commands that the | |
130 | testsuite sends to GDB, for instance if GDB crashes during the run, | |
131 | and you want to reconstruct the sequence of commands. | |
132 | ||
133 | If the DejaGNU variable TRANSCRIPT is set (to any value), each | |
134 | invocation of GDB during the test run will get a transcript file | |
135 | written into the DejaGNU output directory. The file will have the | |
136 | name transcript.<n>, where <n> is an integer. The first line of the | |
137 | file shows the invocation command with all the options passed to it, | |
138 | while subsequent lines are the GDB commands. A `make check' might | |
139 | look like this: | |
140 | ||
141 | make check RUNTESTFLAGS=TRANSCRIPT=y | |
142 | ||
143 | The transcript may not be complete, as for instance tests of command | |
144 | completion may show only partial command lines. | |
145 | ||
146 | GDB | |
147 | ||
148 | By default, the testsuite exercises the GDB in the build directory, | |
149 | but you can set GDB to be a pathname to a different version. For | |
150 | instance, | |
151 | ||
152 | make check RUNTESTFLAGS=GDB=/usr/bin/gdb | |
153 | ||
154 | runs the testsuite on the GDB in /usr/bin. | |
155 | ||
156 | GDBSERVER | |
157 | ||
158 | You can set GDBSERVER to be a particular GDBserver of interest, so for | |
159 | instance | |
160 | ||
161 | make check RUNTESTFLAGS="GDB=/usr/bin/gdb GDBSERVER=/usr/bin/gdbserver" | |
162 | ||
163 | checks both the installed GDB and GDBserver. | |
164 | ||
165 | INTERNAL_GDBFLAGS | |
166 | ||
167 | Command line options passed to all GDB invocations. | |
168 | ||
169 | The default is "-nw -nx". | |
170 | ||
171 | `-nw' disables any of the windowed interfaces. | |
172 | `-nx' disables ~/.gdbinit, so that it doesn't interfere with | |
173 | the tests. | |
174 | ||
175 | This is actually considered an internal variable, and you | |
176 | won't normally want to change it. However, in some situations, | |
177 | this may be tweaked as a last resort if the testsuite doesn't | |
178 | have direct support for the specifics of your environment. | |
179 | The testsuite does not override a value provided by the user. | |
180 | ||
181 | As an example, when testing an installed GDB that has been | |
182 | configured with `--with-system-gdbinit', like by default, | |
183 | you do not want ~/.gdbinit to interfere with tests, but, you | |
184 | may want the system .gdbinit file loaded. As there's no way to | |
185 | ask the testsuite, or GDB, to load the system gdbinit but | |
186 | not ~/.gdbinit, a workaround is then to remove `-nx' from | |
187 | INTERNAL_GDBFLAGS, and point $HOME at a directory without | |
188 | a .gdbinit. For example: | |
189 | ||
190 | cd testsuite | |
191 | HOME=`pwd` runtest \ | |
192 | GDB=/usr/bin/gdb \ | |
193 | GDBSERVER=/usr/bin/gdbserver \ | |
194 | INTERNAL_GDBFLAGS=-nw | |
195 | ||
196 | GDB_PARALLEL | |
197 | ||
e352bf0a PA |
198 | To use parallel testing mode without using the the Makefile, set |
199 | GDB_PARALLEL on the runtest command line to "yes". Before starting | |
200 | the tests, you must ensure that the directories cache, outputs, and | |
201 | temp in the test suite build directory are either empty or have been | |
202 | deleted. cache in particular is used to share data across invocations | |
203 | of runtest, and files there may affect the test results. The Makefile | |
204 | automatically does these deletions. | |
205 | ||
206 | FORCE_PARALLEL | |
207 | ||
208 | Setting FORCE_PARALLEL to any non-empty value forces parallel testing | |
209 | mode even if RUNTESTFLAGS is not empty. | |
b866c52d | 210 | |
51f77c37 PA |
211 | FORCE_SEPARATE_MI_TTY |
212 | ||
213 | Setting FORCE_MI_SEPARATE_UI to 1 forces all MI testing to start GDB | |
214 | in console mode, with MI running on a separate TTY, on a secondary UI | |
215 | started with "new-ui". | |
216 | ||
b866c52d SS |
217 | GDB_INOTIFY |
218 | ||
219 | For debugging parallel mode, it is handy to be able to see when a test | |
220 | case writes to a file outside of its designated output directory. | |
221 | ||
222 | If you have the inotify-tools package installed, you can set the | |
223 | GDB_INOTIFY variable on the runtest command line. This will cause the | |
224 | test suite to watch for parallel-unsafe file creations and report | |
225 | them, both to stdout and in the test suite log file. | |
226 | ||
227 | This setting is only meaningful in conjunction with GDB_PARALLEL. | |
228 | ||
c17ef0d5 DE |
229 | TESTS |
230 | ||
231 | This variable is used to specify which set of tests to run. | |
232 | It is passed to make (not runtest) and its contents are a space separated | |
233 | list of tests to run. | |
234 | ||
235 | If using GNU make then the contents are wildcard-expanded using | |
236 | GNU make's $(wildcard) function. Test paths must be fully specified, | |
237 | relative to the "testsuite" subdirectory. This allows one to run all | |
4992aa20 JM |
238 | tests in a subdirectory by passing "gdb.subdir/*.exp", or more simply |
239 | by using the check-gdb.subdir target in the Makefile. | |
240 | ||
c17ef0d5 DE |
241 | If for some strange reason one wanted to run all tests that begin with |
242 | the letter "d" that is also possible: TESTS="*/d*.exp". | |
243 | ||
244 | Do not write */*.exp to specify all tests (assuming all tests are only | |
245 | nested one level deep, which is not necessarily true). This will pick up | |
246 | .exp files in ancillary directories like "lib" and "config". | |
247 | Instead write gdb.*/*.exp. | |
248 | ||
249 | Example: | |
250 | ||
251 | make -j10 check TESTS="gdb.server/[s-w]*.exp */x*.exp" | |
252 | ||
253 | If not using GNU make then the value is passed directly to runtest. | |
254 | If not specified, all tests are run. | |
b866c52d | 255 | |
2a31c623 PA |
256 | READ1 |
257 | ||
258 | This make (not runtest) variable is used to specify whether the | |
259 | testsuite preloads the read1.so library into expect. Any non-empty | |
260 | value means true. See "Race detection" below. | |
261 | ||
c7ab0aef SDJ |
262 | GDB_TEST_SOCKETHOST |
263 | ||
264 | This variable can provide the hostname/address that should be used | |
265 | when performing GDBserver-related tests. This is useful in some | |
266 | situations, e.g., when you want to test the IPv6 connectivity of GDB | |
267 | and GDBserver, or when using a different hostname/address is needed. | |
268 | For example, to make GDB and GDBserver use IPv6-only connections, you | |
269 | can do: | |
270 | ||
271 | make check TESTS="gdb.server/*.exp" RUNTESTFLAGS='GDB_TEST_SOCKETHOST=tcp6:[::1]' | |
272 | ||
273 | Note that only a hostname/address can be provided, without a port | |
274 | number. | |
275 | ||
f63c03b4 SDJ |
276 | TS |
277 | ||
278 | This variable turns on the timestamp printing for each line of "make | |
279 | check". Note that the timestamp will be printed on stdout output | |
280 | only. In other words, there will be no timestamp output on either | |
281 | gdb.sum and gdb.log files. If you would like to enable timestamp | |
282 | printing, you can do: | |
283 | ||
284 | make check TS=1 | |
285 | ||
286 | TS_FORMAT | |
287 | ||
288 | You can provide a custom format for timestamp printing with this | |
289 | variable. The format must be a string compatible with "strftime". | |
290 | This variable is only useful when the TS variable is also provided. | |
291 | If you would like to change the output format of the timestamp, you | |
292 | can do: | |
293 | ||
294 | make check TS=1 TS_FORMAT='[%b %H:%S]' | |
295 | ||
2a31c623 PA |
296 | Race detection |
297 | ************** | |
298 | ||
299 | The testsuite includes a mechanism that helps detect test races. | |
300 | ||
301 | For example, say the program running under expect outputs "abcd", and | |
302 | a test does something like this: | |
303 | ||
304 | expect { | |
305 | "a.*c" { | |
306 | } | |
307 | "b" { | |
308 | } | |
309 | "a" { | |
310 | } | |
311 | } | |
312 | ||
313 | Which case happens to match depends on what expect manages to read | |
314 | into its internal buffer in one go. If it manages to read three bytes | |
315 | or more, then the first case matches. If it manages to read two | |
316 | bytes, then the second case matches. If it manages to read only one | |
317 | byte, then the third case matches. | |
318 | ||
319 | To help detect these cases, the race detection mechanism preloads a | |
320 | library into expect that forces the `read' system call to always | |
321 | return at most 1 byte. | |
322 | ||
323 | To enable this, either pass a non-empty value in the READ1 make | |
324 | variable, or use the check-read1 make target instead of check. | |
325 | ||
326 | Examples: | |
327 | ||
328 | make -j10 check-read1 TESTS="*/paginate-*.exp" | |
329 | make -j10 check READ1="1" | |
330 | ||
b866c52d SS |
331 | Testsuite Configuration |
332 | *********************** | |
333 | ||
334 | It is possible to adjust the behavior of the testsuite by defining | |
335 | the global variables listed below, either in a `site.exp' file, | |
336 | or in a board file. | |
337 | ||
338 | gdb_test_timeout | |
339 | ||
340 | Defining this variable changes the default timeout duration used | |
341 | during communication with GDB. More specifically, the global variable | |
342 | used during testing is `timeout', but this variable gets reset to | |
343 | `gdb_test_timeout' at the beginning of each testcase, which ensures | |
344 | that any local change to `timeout' in a testcase does not affect | |
345 | subsequent testcases. | |
346 | ||
347 | This global variable comes in handy when the debugger is slower than | |
348 | normal due to the testing environment, triggering unexpected `TIMEOUT' | |
349 | test failures. Examples include when testing on a remote machine, or | |
350 | against a system where communications are slow. | |
351 | ||
352 | If not specifically defined, this variable gets automatically defined | |
353 | to the same value as `timeout' during the testsuite initialization. | |
354 | The default value of the timeout is defined in the file | |
355 | `testsuite/config/unix.exp' (at least for Unix hosts; board files may | |
356 | have their own values). | |
357 | ||
8b696e31 YQ |
358 | gdb_reverse_timeout |
359 | ||
360 | Defining this variable changes the default timeout duration when tests | |
361 | under gdb.reverse directory are running. Process record and reverse | |
362 | debugging is so slow that its tests have unexpected `TIMEOUT' test | |
363 | failures. This global variable is useful to bump up the value of | |
364 | `timeout' for gdb.reverse tests and doesn't cause any delay where | |
365 | actual failures happen in the rest of the testsuite. | |
366 | ||
b866c52d SS |
367 | |
368 | Board Settings | |
369 | ************** | |
370 | ||
371 | DejaGNU includes the concept of a "board file", which specifies | |
372 | testing details for a particular target (which are often bare circuit | |
373 | boards, thus the name). | |
374 | ||
375 | In the GDB testsuite specifically, the board file may include a | |
376 | number of "board settings" that test cases may check before deciding | |
377 | whether to exercise a particular feature. For instance, a board | |
378 | lacking any I/O devices, or perhaps simply having its I/O devices | |
379 | not wired up, should set `noinferiorio'. | |
380 | ||
381 | Here are the supported board settings: | |
382 | ||
383 | gdb,cannot_call_functions | |
384 | ||
385 | The board does not support inferior call, that is, invoking inferior | |
386 | functions in GDB. | |
387 | ||
388 | gdb,can_reverse | |
389 | ||
390 | The board supports reverse execution. | |
391 | ||
392 | gdb,no_hardware_watchpoints | |
393 | ||
394 | The board does not support hardware watchpoints. | |
395 | ||
396 | gdb,nofileio | |
397 | ||
398 | GDB is unable to intercept target file operations in remote and | |
399 | perform them on the host. | |
400 | ||
401 | gdb,noinferiorio | |
402 | ||
403 | The board is unable to provide I/O capability to the inferior. | |
404 | ||
405 | gdb,noresults | |
406 | ||
407 | A program will not return an exit code or result code (or the value | |
408 | of the result is undefined, and should not be looked at). | |
409 | ||
410 | gdb,nosignals | |
411 | ||
412 | The board does not support signals. | |
413 | ||
414 | gdb,skip_huge_test | |
415 | ||
416 | Skip time-consuming tests on the board with slow connection. | |
417 | ||
418 | gdb,skip_float_tests | |
419 | ||
420 | Skip tests related to floating point. | |
421 | ||
422 | gdb,use_precord | |
423 | ||
424 | The board supports process record. | |
425 | ||
a25eb028 MR |
426 | gdb_init_command |
427 | gdb_init_commands | |
428 | ||
429 | Commands to send to GDB every time a program is about to be run. The | |
430 | first of these settings defines a single command as a string. The | |
431 | second defines a TCL list of commands being a string each. The commands | |
432 | are sent one by one in a sequence, first from `gdb_init_command', if any, | |
433 | followed by individual commands from `gdb_init_command', if any, in this | |
434 | list's order. | |
435 | ||
b866c52d SS |
436 | gdb_server_prog |
437 | ||
438 | The location of GDBserver. If GDBserver somewhere other than its | |
439 | default location is used in test, specify the location of GDBserver in | |
440 | this variable. The location is a file name for GDBserver, and may be | |
441 | either absolute or relative to the testsuite subdirectory of the build | |
442 | directory. | |
443 | ||
444 | in_proc_agent | |
445 | ||
446 | The location of the in-process agent (used for fast tracepoints and | |
447 | other special tests). If the in-process agent of interest is anywhere | |
448 | other than its default location, set this variable. The location is a | |
449 | filename, and may be either absolute or relative to the testsuite | |
450 | subdirectory of the build directory. | |
451 | ||
452 | noargs | |
453 | ||
454 | GDB does not support argument passing for inferior. | |
455 | ||
456 | no_long_long | |
457 | ||
458 | The board does not support type long long. | |
459 | ||
460 | use_cygmon | |
461 | ||
462 | The board is running the monitor Cygmon. | |
463 | ||
464 | use_gdb_stub | |
465 | ||
466 | The tests are running with a GDB stub. | |
467 | ||
b477a5e6 PA |
468 | exit_is_reliable |
469 | ||
470 | Set to true if GDB can assume that letting the program run to end | |
471 | reliably results in program exits being reported as such, as opposed | |
472 | to, e.g., the program ending in an infinite loop or the board | |
473 | crashing/resetting. If not set, this defaults to $use_gdb_stub. In | |
474 | other words, native targets are assumed reliable by default, and | |
475 | remote stubs assumed unreliable. | |
476 | ||
b866c52d SS |
477 | gdb,predefined_tsv |
478 | ||
479 | The predefined trace state variables the board has. | |
480 | ||
f6512a69 SM |
481 | gdb,no_thread_names |
482 | ||
483 | The target doesn't support thread names. | |
b866c52d SS |
484 | |
485 | Testsuite Organization | |
486 | ********************** | |
487 | ||
488 | The testsuite is entirely contained in `gdb/testsuite'. The main | |
489 | directory of the testsuite includes some makefiles and configury, but | |
490 | these are minimal, and used for little besides cleaning up, since the | |
491 | tests themselves handle the compilation of the programs that GDB will | |
492 | run. | |
493 | ||
494 | The file `testsuite/lib/gdb.exp' contains common utility procs useful | |
495 | for all GDB tests, while the directory testsuite/config contains | |
496 | configuration-specific files, typically used for special-purpose | |
497 | definitions of procs like `gdb_load' and `gdb_start'. | |
498 | ||
499 | The tests themselves are to be found in directories named | |
500 | 'testsuite/gdb.* and subdirectories of those. The names of the test | |
501 | files must always end with ".exp". DejaGNU collects the test files by | |
502 | wildcarding in the test directories, so both subdirectories and | |
503 | individual files typically get chosen and run in alphabetical order. | |
504 | ||
505 | The following lists some notable types of subdirectories and what they | |
506 | are for. Since DejaGNU finds test files no matter where they are | |
507 | located, and since each test file sets up its own compilation and | |
508 | execution environment, this organization is simply for convenience and | |
509 | intelligibility. | |
510 | ||
511 | gdb.base | |
512 | ||
513 | This is the base testsuite. The tests in it should apply to all | |
514 | configurations of GDB (but generic native-only tests may live here). | |
515 | The test programs should be in the subset of C that is both valid | |
516 | ANSI/ISO C, and C++. | |
517 | ||
518 | gdb.<lang> | |
519 | ||
520 | Language-specific tests for any language besides C. Examples are | |
9c37b5ae | 521 | gdb.cp for C++ and gdb.rust for Rust. |
b866c52d SS |
522 | |
523 | gdb.<platform> | |
524 | ||
525 | Non-portable tests. The tests are specific to a specific | |
bc23328c | 526 | configuration (host or target), such as eCos. |
b866c52d SS |
527 | |
528 | gdb.arch | |
529 | ||
530 | Architecture-specific tests that are (usually) cross-platform. | |
531 | ||
532 | gdb.<subsystem> | |
533 | ||
534 | Tests that exercise a specific GDB subsystem in more depth. For | |
535 | instance, gdb.disasm exercises various disassemblers, while | |
536 | gdb.stabs tests pathways through the stabs symbol reader. | |
537 | ||
71c0c615 YQ |
538 | gdb.perf |
539 | ||
540 | GDB performance tests. | |
541 | ||
b866c52d SS |
542 | Writing Tests |
543 | ************* | |
544 | ||
545 | In many areas, the GDB tests are already quite comprehensive; you | |
546 | should be able to copy existing tests to handle new cases. Be aware | |
547 | that older tests may use obsolete practices but have not yet been | |
548 | updated. | |
549 | ||
550 | You should try to use `gdb_test' whenever possible, since it includes | |
551 | cases to handle all the unexpected errors that might happen. However, | |
552 | it doesn't cost anything to add new test procedures; for instance, | |
553 | gdb.base/exprs.exp defines a `test_expr' that calls `gdb_test' | |
554 | multiple times. | |
555 | ||
556 | Only use `send_gdb' and `gdb_expect' when absolutely necessary. Even | |
557 | if GDB has several valid responses to a command, you can use | |
558 | `gdb_test_multiple'. Like `gdb_test', `gdb_test_multiple' recognizes | |
559 | internal errors and unexpected prompts. | |
560 | ||
561 | Do not write tests which expect a literal tab character from GDB. On | |
562 | some operating systems (e.g. OpenBSD) the TTY layer expands tabs to | |
563 | spaces, so by the time GDB's output reaches `expect' the tab is gone. | |
564 | ||
565 | The source language programs do *not* need to be in a consistent | |
566 | style. Since GDB is used to debug programs written in many different | |
567 | styles, it's worth having a mix of styles in the testsuite; for | |
568 | instance, some GDB bugs involving the display of source lines might | |
569 | never manifest themselves if the test programs used GNU coding style | |
570 | uniformly. | |
571 | ||
572 | Some testcase results need more detailed explanation: | |
573 | ||
574 | KFAIL | |
575 | ||
576 | Use KFAIL for known problem of GDB itself. You must specify the GDB | |
577 | bug report number, as in these sample tests: | |
578 | ||
579 | kfail "gdb/13392" "continue to marker 2" | |
580 | ||
581 | or | |
582 | ||
583 | setup_kfail gdb/13392 "*-*-*" | |
584 | kfail "continue to marker 2" | |
585 | ||
586 | ||
587 | XFAIL | |
588 | ||
589 | Short for "expected failure", this indicates a known problem with the | |
590 | environment. This could include limitations of the operating system, | |
591 | compiler version, and other components. | |
592 | ||
593 | This example from gdb.base/attach-pie-misread.exp is a sanity check | |
594 | for the target environment: | |
595 | ||
596 | # On x86_64 it is commonly about 4MB. | |
597 | if {$stub_size > 25000000} { | |
598 | xfail "stub size $stub_size is too large" | |
599 | return | |
600 | } | |
601 | ||
602 | You should provide bug report number for the failing component of the | |
603 | environment, if such bug report is available, as with this example | |
604 | referring to a GCC problem: | |
605 | ||
606 | if {[test_compiler_info {gcc-[0-3]-*}] | |
607 | || [test_compiler_info {gcc-4-[0-5]-*}]} { | |
608 | setup_xfail "gcc/46955" *-*-* | |
609 | } | |
610 | gdb_test "python print ttype.template_argument(2)" "&C::c" | |
611 | ||
612 | Note that it is also acceptable, and often preferable, to avoid | |
613 | running the test at all. This is the better option if the limitation | |
614 | is intrinsic to the environment, rather than a bug expected to be | |
615 | fixed in the near future. | |
739b3f1d PA |
616 | |
617 | Local vs Remote vs Native | |
618 | ************************* | |
619 | ||
620 | It's unfortunately easy to get confused in the testsuite about what's | |
621 | native and what's not, what's remote and what's not. The confusion is | |
622 | caused by the overlap in vocabulary between DejaGnu and GDB. | |
623 | ||
624 | From a DejaGnu point of view: | |
625 | ||
626 | - native: the host or target board is considered native if the its | |
627 | triplet is the same as the build system's triplet, | |
628 | ||
629 | - remote: the host or target board is considered remote if it's | |
630 | running on a different machine, and thus require ssh, for example, | |
631 | to run commands, versus simply running commands directly. | |
632 | ||
633 | Note that they are not mutually exclusive, as you can have a remote | |
634 | machine that has the same triplet as the build machine. | |
635 | ||
636 | From a GDB point of view: | |
637 | ||
638 | - native: when GDB uses system calls such as ptrace to interact | |
639 | directly with processes on the same system its running on, | |
640 | ||
641 | - remote: when GDB speaks the RSP (Remote Serial Protocol) with | |
642 | another program doing the ptrace stuff. | |
643 | ||
644 | Note that they are mutually exclusive. An inferior can only be either | |
645 | debugged with the native target, or with the remote target a specific | |
646 | time. | |
647 | ||
648 | That means that there are cases where the target is not remote for | |
649 | DejaGnu, but is remote for GDB (e.g. running GDBserver on the same | |
650 | machine). | |
651 | ||
652 | You can also have a remote target for DejaGnu, but native for GDB | |
653 | (e.g. building on x86 a GDB that runs on ARM and running the | |
654 | testsuite with a remote host). | |
655 | ||
656 | Therefore, care must be taken to check for the right kind of remote. | |
657 | Use [is_remote target] to check whether the DejaGnu target board is | |
658 | remote. When what you really want to know is whether GDB is using the | |
659 | remote protocol, because feature X is only available when GDB debugs | |
660 | natively, check gdb_protocol instead. |