gdb.base/warning.exp tweaks
authorPedro Alves <palves@redhat.com>
Mon, 19 Nov 2018 15:08:46 +0000 (15:08 +0000)
committerPedro Alves <palves@redhat.com>
Mon, 19 Nov 2018 15:08:46 +0000 (15:08 +0000)
commit6769f2765db0d94eeb8437b41a925e2bd871f514
tree7af7e344742bfe549e4ee9d701a7c248c8fbe3e8
parent4f323b727743e40ce9b0bde1e19a73b4586c2f25
gdb.base/warning.exp tweaks

#1- Check that the warning is emitted.

#2- Avoid overriding INTERNAL_GDBFLAGS, as per documentated in
    gdb/testsuite/README:

 ~~~
 The testsuite does not override a value provided by the user.
 ~~~

We don't actually need to tweak INTERNAL_GDBFLAGS, we just need to
append out -data-directory to GDBFLAGS, because each passed
-data-directory option leads to a call to the warning:

 $ ./gdb -data-directory=foo -data-directory=bar
 Warning: foo: No such file or directory.
 Warning: bar: No such file or directory.
 [...]

gdb/ChangeLog
2018-11-19  Pedro Alves  <palves@redhat.com>

* gdb.base/warning.exp: Don't override INTERNAL_FLAGS.  Use
gdb_spawn_with_cmdline_opts instead of gdb_start.  Check that we
see the expected warning.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/warning.exp