Stop using nowarnings in gdb/testsuite/gdb.multi/
authorPedro Alves <palves@redhat.com>
Thu, 10 Dec 2015 16:21:06 +0000 (16:21 +0000)
committerPedro Alves <palves@redhat.com>
Thu, 10 Dec 2015 16:21:06 +0000 (16:21 +0000)
commit762f774785f4ef878ac4c831e1f4733dc957234d
tree841a8e15b74ae9f960ee29087afce1df96cc6b7d
parent4a07dc81356ed8728e204e9aabeb256703c59aef
Stop using nowarnings in gdb/testsuite/gdb.multi/

Several of the gdb.multi tests use the "nowarnings" option to suppress
warnings.  The warnings in question all come from missing headers,
like e.g.:

 src/gdb/testsuite/gdb.multi/multi-arch-exec.c:28:3: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default]
    exit (1);
    ^

There's no point in trying to avoid to include standard headers.  In
gdb.base/hangout.c's case, it's even dangerous, as that file calls
printf.  In order to compile a call to a variatic function correctly,
a declaration must be visible.

gdb/testsuite/ChangeLog:
2015-12-10  Pedro Alves  <palves@redhat.com>

* gdb.multi/base.exp: Don't use nowarnings.
* gdb.multi/bkpt-multi-exec.exp: Don't use nowarnings.
* gdb.multi/hangout.c: Include stdio.h.
* gdb.multi/hello.c: Include stdlib.h.
* gdb.multi/multi-arch-exec.c: Include stdlib.h.
* gdb.multi/multi-arch-exec.exp: Don't use nowarnings.
* gdb.multi/multi-arch.exp: Don't use nowarnings.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.multi/base.exp
gdb/testsuite/gdb.multi/bkpt-multi-exec.exp
gdb/testsuite/gdb.multi/hangout.c
gdb/testsuite/gdb.multi/hello.c
gdb/testsuite/gdb.multi/multi-arch-exec.c
gdb/testsuite/gdb.multi/multi-arch-exec.exp
gdb/testsuite/gdb.multi/multi-arch.exp