diff options
| author | Yao Qi <yao.qi@linaro.org> | 2016-09-22 16:04:03 +0100 |
|---|---|---|
| committer | Yao Qi <yao.qi@linaro.org> | 2016-09-22 16:04:03 +0100 |
| commit | f73842fc847e297fd44542de9601a84b4d6b28d8 (patch) | |
| tree | e4001c969de7f910c0032c259b7540ea1379f204 /opcodes/m32c-opc.c | |
| parent | de6784544abc97d5e396cb1e83eda1ae09f63d40 (diff) | |
| download | gdb-f73842fc847e297fd44542de9601a84b4d6b28d8.zip gdb-f73842fc847e297fd44542de9601a84b4d6b28d8.tar.gz gdb-f73842fc847e297fd44542de9601a84b4d6b28d8.tar.bz2 | |
Close gdbserver in mi_gdb_exit
In commit 6423214f (testsuite: Don't use expect_background to reap
gdbserver), we override gdb_exit in lib/gdbserver-support.exp, so
that we can close gdbserver first. However, we don't close gdbserver
in mi_gdb_exit. This makes a problem in my aarch64 mulit-arch testing,
in which I run some mi tests, mi-watch.exp for example, in different
variations (aarch64 and arm),
Schedule of variations:
junor0-2
junor0-2-arm/-marm
junor0-2-arm/-mthumb
When the test is done in the first variation (aarch64), test case is
recompiled for arm, but GDBserver with aarch64 program is still
running. When the second variation is started, GDB loads arm program,
but GDBserver still loads aarch64 program because the old GDBserver
process is using it. We'll get,
47-target-select remote junor0-2:2350^M
&"warning: Selected architecture arm is not compatible with reported target architecture aarch64\n"^M
&"warning: Architecture rejected target-supplied description\n"
This patch fixes this problem by closing GDBserver in mi_gdb_exit.
gdb/testsuite:
2016-09-22 Yao Qi <yao.qi@linaro.org>
* lib/gdbserver-support.exp: Rename mi_gdb_exit.
(gdb_exit): Rename it to ...
(gdbserver_gdb_exit): ... Close GDBserver.
(gdb_exit): New proc, call gdbserver_gdb_exit.
(mi_gdb_exit): Likewise.
Diffstat (limited to 'opcodes/m32c-opc.c')
0 files changed, 0 insertions, 0 deletions