public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Close gdbserver in mi_gdb_exit Date: Fri, 23 Sep 2016 00:46:00 -0000 [thread overview] Message-ID: <f73842fc847e297fd44542de9601a84b4d6b28d8@gdb-build> (raw) *** TEST RESULTS FOR COMMIT f73842fc847e297fd44542de9601a84b4d6b28d8 *** Author: Yao Qi <yao.qi@linaro.org> Branch: master Commit: f73842fc847e297fd44542de9601a84b4d6b28d8 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.
next reply other threads:[~2016-09-22 19:54 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-09-23 0:46 sergiodj+buildbot [this message] 2016-09-23 0:46 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot 2016-09-23 1:31 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2016-09-23 1:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-23 2:04 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2016-09-23 12:21 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2016-09-23 16:38 ` Failures on Debian-i686, " sergiodj+buildbot 2016-09-23 23:27 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2016-09-24 0:45 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-24 1:42 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-25 20:17 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2016-09-25 21:05 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-26 3:52 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-09-26 3:55 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=f73842fc847e297fd44542de9601a84b4d6b28d8@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).