diff options
| author |   Don Breazeal <donb@codesourcery.com> | 2015-12-14 11:18:05 -0800 |
|---|---|---|
| committer | Don Breazeal <donb@codesourcery.com> | 2015-12-14 11:18:05 -0800 |
| commit | a8f077dc25b1732fb272a7ff10f72b5ca6f67b70 (patch) | |
| tree | 73b4c90b87cb6fc66300ade3dc2d41d871ab00fe /gdb/testsuite/gdb.base/foll-vfork.exp | |
| parent | [AArch64][PATCH 14/14] Support FP16 Adv.SIMD Scalar Shift By Immediate instru... (diff) | |
| download | binutils-gdb-a8f077dc25b1732fb272a7ff10f72b5ca6f67b70.tar.gz binutils-gdb-a8f077dc25b1732fb272a7ff10f72b5ca6f67b70.tar.bz2 binutils-gdb-a8f077dc25b1732fb272a7ff10f72b5ca6f67b70.zip | |
Target remote mode fork and exec test updates
This patch updates tests for fork and exec events in target remote mode.
In the majority of cases this was a simple matter of removing some code
that disabled the test for target remote. In a few cases the test needed
to be disabled; in those cases the gdb_protocol was checked instead of
using the [is_remote target] etc.
In a couple of cases we needed to use clean_restart, since target remote
doesn't support the run command, and in one case we had to modify an expect
expression to allow for a "multiprocess-style" ptid.
Tested with the patch that implemented target remote mode fork and exec
event support.
gdb/testsuite/ChangeLog:
* gdb.base/execl-update-breakpoints.exp (main): Enable for target
remote.
* gdb.base/foll-exec-mode.exp (main): Disable for target remote.
* gdb.base/foll-exec.exp (main): Enable for target remote.
* gdb.base/foll-fork.exp (main): Likewise.
* gdb.base/foll-vfork.exp (main): Likewise.
* gdb.base/multi-forks.exp (main): Likewise, and use clean_restart.
(proc continue_to_exit_bp_loc): Use clean_restart.
* gdb.base/pie-execl.exp (main): Disable for target remote.
* gdb.base/watch-vfork.exp (main): Enable for target remote.
* gdb.mi/mi-nsthrexec.exp (main): Likewise.
* gdb.threads/execl.exp (main): Likewise.
* gdb.threads/fork-child-threads.exp (main): Likewise.
* gdb.threads/fork-plus-threads.exp (main): Disable for target
remote.
* gdb.threads/fork-thread-pending.exp (main): Enable for target
remote.
* gdb.threads/linux-dp.exp (check_philosopher_stack): Allow
pid.tid style ptids, instead of just tid.
* gdb.threads/thread-execl.exp (main): Enable for target remote.
* gdb.threads/watchpoint-fork.exp (main): Likewise.
* gdb.trace/report.exp (use_collected_data): Allow pid.tid style
ptids, instead of just tid.
Diffstat (limited to 'gdb/testsuite/gdb.base/foll-vfork.exp')
| -rw-r--r-- | gdb/testsuite/gdb.base/foll-vfork.exp | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/gdb/testsuite/gdb.base/foll-vfork.exp b/gdb/testsuite/gdb.base/foll-vfork.exp index 82922d82a95..0659509776f 100644 --- a/gdb/testsuite/gdb.base/foll-vfork.exp +++ b/gdb/testsuite/gdb.base/foll-vfork.exp @@ -18,10 +18,6 @@ # either execs or exits --- since those events take somewhat different # code paths in GDB, both variants are exercised. -if { [is_remote target] || ![isnative] } then { - continue -} - # Until "set follow-fork-mode" and "catch vfork" are implemented on # other targets... # |