[Bug gdb/18208] Fails in gdb.base/coredump-filter.exp in remote testing

["palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18208

--- Comment #8 from Pedro Alves <palves at redhat dot com> ---
BTW, we have other similar uses of sh -c in the tree:

$ grep remote_exec -rn | grep "sh -"
gdb.base/coredump-filter.exp:34:    remote_exec target "sh -c \"echo
$filter_flag > /proc/$ipid/coredump_filter\""
gdb.trace/strace.exp:76:    set status [remote_exec target "sh -c { \[ -S
$socket_file \] }"]
gdb.trace/strace.exp:98:        set status [remote_exec target "sh -c { \[ -S
$socket_file \] }"]
gdb.trace/strace.exp:116:       remote_exec target "sh -c \"rm -r
$socket_file\""
gdb.dwarf2/dw2-dir-file-name.exp:359:remote_exec host "sh -c \"rm -f
$filelist\""
gdb.dwarf2/dw2-dir-file-name.exp:360:remote_exec host "sh -c \"rmdir
$dirremovelist\""
gdb.dwarf2/dw2-dir-file-name.exp:361:remote_exec host "sh -c \"mkdir
$dircreatelist\""
gdb.dwarf2/dw2-dir-file-name.exp:362:remote_exec host "sh -c \"for d in
$dircreatelist; do cp ${srcdir}/${subdir}/${srcfile} \\\$d/${srctmpfile};
done\""

so it sounds like the issue may be on your board file.  I haven't tried it
through a board file myself though.  We should probably have a board file that
does real remote gdbserver testing against localhost...

-- 
You are receiving this mail because:
You are on the CC list for the bug.