From patchwork Wed Oct 8 06:27:59 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yao Qi X-Patchwork-Id: 3132 Received: (qmail 31318 invoked by alias); 8 Oct 2014 06:32:35 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Delivered-To: mailing list gdb-patches@sourceware.org Received: (qmail 31240 invoked by uid 89); 8 Oct 2014 06:32:35 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL, BAYES_00 autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 Oct 2014 06:32:33 +0000 Received: from svr-orw-fem-06.mgc.mentorg.com ([147.34.97.120]) by relay1.mentorg.com with esmtp id 1XbknW-00023F-Le from Yao_Qi@mentor.com ; Tue, 07 Oct 2014 23:32:30 -0700 Received: from qiyao.dyndns.org.com (147.34.91.1) by SVR-ORW-FEM-06.mgc.mentorg.com (147.34.97.120) with Microsoft SMTP Server id 14.3.181.6; Tue, 7 Oct 2014 23:32:29 -0700 From: Yao Qi To: CC: Subject: [PATCH 3/3] Use command "monitor set debug 0" to check the connection Date: Wed, 8 Oct 2014 14:27:59 +0800 Message-ID: <1412749679-27076-4-git-send-email-yao@codesourcery.com> In-Reply-To: <1412749679-27076-1-git-send-email-yao@codesourcery.com> References: <543404EF.4010306@redhat.com> <1412749679-27076-1-git-send-email-yao@codesourcery.com> MIME-Version: 1.0 X-IsSubscribed: yes Nowadays, we are using command "tstatus" to send a packet to GDBserver in order to check the connection. However, on the target doesn't support tracepoint, the following error is emitted before sending any packet to GDBserver. tstatus^M Trace can not be run on this target.^M (gdb) FAIL: gdb.server/server-kill.exp: tstatus We have to choose other commands which exists on different targets, and send a RSP packet to GDBserver. "monitor set debug 0" is a good one. gdb/testsuite: 2014-10-08 Yao Qi * gdb.server/server-kill.exp: Execute command "monitor set debug 0" instead of "tstatus". --- gdb/testsuite/gdb.server/server-kill.exp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gdb/testsuite/gdb.server/server-kill.exp b/gdb/testsuite/gdb.server/server-kill.exp index 0f808a9..a2e65a4 100644 --- a/gdb/testsuite/gdb.server/server-kill.exp +++ b/gdb/testsuite/gdb.server/server-kill.exp @@ -53,4 +53,4 @@ remote_exec target "kill -9 $server_pid" # Force GDB to talk with GDBserver, so that we can get the # "connection closed" error. -gdb_test "tstatus" {Remote connection closed|Remote communication error\. Target disconnected\.: Connection reset by peer\.} +gdb_test "monitor set debug 0" {Remote connection closed|Remote communication error\. Target disconnected\.: Connection reset by peer\.}