aboutsummaryrefslogtreecommitdiff
path: root/gdb/registry.c
diff options
context:
space:
mode:
authorYao Qi <yao@codesourcery.com>2014-08-28 21:27:40 +0800
committerYao Qi <yao@codesourcery.com>2014-09-16 19:13:01 +0800
commit666d413cc37ef7f841abf3e8faf2c3cbc7c5b456 (patch)
tree6b8390c09e1f43cbbe573b94a842907560024273 /gdb/registry.c
parent1c8f6a4d1fcca9e56ac705a224778bf690122a07 (diff)
downloadgdb-666d413cc37ef7f841abf3e8faf2c3cbc7c5b456.zip
gdb-666d413cc37ef7f841abf3e8faf2c3cbc7c5b456.tar.gz
gdb-666d413cc37ef7f841abf3e8faf2c3cbc7c5b456.tar.bz2
Another board file for remote host
In the recent review to my patch about copying files to remote host, we find that we need a board file which is more closely mapped real remote host testing to improve coverage. With the board file local-remote-host-native.exp, DejaGNU copies files to $build/gdb/testsuite/remote-host to emulate the effect of remote host. Is it OK? gdb/testsuite: 2014-09-16 Yao Qi <yao@codesourcery.com> * boards/local-remote-host-native.exp: New file.
Diffstat (limited to 'gdb/registry.c')
0 files changed, 0 insertions, 0 deletions