forked from Imagelibrary/binutils-gdb
6579312c44
The gdb.mi/mi-logging.exp testcase sends a sequence of execution commands to the GDB terminal while the inferior is running, like this: send_gdb "1002-exec-step\n" send_gdb "1003-exec-next\n" expecting that GDB will consume the "1003-exec-next" intput after the inferior stops for the 1002-exec-step. That's a flawed assumption in general, because the inferior itself could consume the "1003-exec-next" input while it is stepping. When GDB puts the inferior in its own terminal, while the inferior is running, GDB marshals input from its terminal to the inferior's terminal. The result is that input typed while the inferior is running never goes to GDB, and so the test fails. The previous patch addressed issues like this by making the inferior and GDB share the same terminal for tests that really wanted to test some aspect of a shared terminal. For gdb.mi/mi-logging.exp though, there's really no reason to send input while the program is running, so the fix here is to stop it from doing so. While debugging the testcase, I ran into the fact that it reuses the same log file for more than one [open] sequence, overwriting previous runs. The testcase also deletes the log files at the very end, which makes it impossible to inspect the logs after a failure run. The patch addresses those issues as well. gdb/testsuite/ChangeLog: yyyy-mm-dd Pedro Alves <pedro@palves.net> * gdb.mi/mi-logging.exp: Do not reuse log files for different runs. Delete logs at the start of the testcase, not at the end. (wait_open, gdb_test_file): New procedures. Use them. Change-Id: Ife215a82391a020041fd05478bd8dbee6e04d607
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.