diff options
author | Pedro Alves <palves@redhat.com> | 2015-12-10 16:21:06 +0000 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2015-12-10 16:21:06 +0000 |
commit | 762f774785f4ef878ac4c831e1f4733dc957234d (patch) | |
tree | 841a8e15b74ae9f960ee29087afce1df96cc6b7d /opcodes/mips-dis.c | |
parent | 4a07dc81356ed8728e204e9aabeb256703c59aef (diff) | |
download | gdb-762f774785f4ef878ac4c831e1f4733dc957234d.zip gdb-762f774785f4ef878ac4c831e1f4733dc957234d.tar.gz gdb-762f774785f4ef878ac4c831e1f4733dc957234d.tar.bz2 |
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.
Diffstat (limited to 'opcodes/mips-dis.c')
0 files changed, 0 insertions, 0 deletions