diff options
| author | Pedro Alves <palves@redhat.com> | 2017-10-12 18:36:08 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2017-10-12 18:39:13 +0100 |
| commit | 4e04f0450f83d8d0ad08579b5e6c8b4e8a8e693f (patch) | |
| tree | 80075ec7a280f03469d72a515dd070aecfd2497a /gdb/m32c-tdep.c | |
| parent | 871a186e41aeb7f966c6570b8f1659aec9d2c15d (diff) | |
| download | gdb-4e04f0450f83d8d0ad08579b5e6c8b4e8a8e693f.zip gdb-4e04f0450f83d8d0ad08579b5e6c8b4e8a8e693f.tar.gz gdb-4e04f0450f83d8d0ad08579b5e6c8b4e8a8e693f.tar.bz2 | |
Enable gdb.base/inferior-died.exp on is_remote target boards
We support follow-fork in the remote protocol nowadays.
Also, the right way to enable non-stop mode is to do it before
connecting, and for use_gdb_stub boards, that means we have to do it
at gdb_load time. The "modern" pattern for that is to pass non-stop
in GDBFLAGS.
This makes the test pass with --target_board=native-gdbserver.
gdb/testsuite/ChangeLog:
2017-10-12 Pedro Alves <palves@redhat.com>
Simon Marchi <simon.marchi@polymtl.ca>
* gdb.base/inferior-died.exp: Remove is_remote and isnative
checks. Use build_executable + clean_restart instead of
prepare_for_testing. Pass "set non-stop on" via GDBFLAGS instead
of enabling non-stop after starting gdb.
Diffstat (limited to 'gdb/m32c-tdep.c')
0 files changed, 0 insertions, 0 deletions