From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26651 invoked by alias); 8 Oct 2014 14:19:49 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 26641 invoked by uid 89); 8 Oct 2014 14:19:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 08 Oct 2014 14:19:47 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s98EJgUg000732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 8 Oct 2014 10:19:43 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s98EJeAo022912; Wed, 8 Oct 2014 10:19:41 -0400 Message-ID: <543547FC.30306@redhat.com> Date: Wed, 08 Oct 2014 14:19:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Yao Qi , gdb-patches@sourceware.org Subject: Re: [PATCH 3/3] Use command "monitor set debug 0" to check the connection References: <543404EF.4010306@redhat.com> <1412749679-27076-1-git-send-email-yao@codesourcery.com> <1412749679-27076-4-git-send-email-yao@codesourcery.com> In-Reply-To: <1412749679-27076-4-git-send-email-yao@codesourcery.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-10/txt/msg00151.txt.bz2 On 10/08/2014 07:27 AM, Yao Qi wrote: > 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. > Hmm, are you sure GDB didn't really send any packet to GDBserver? That error is printed by trace_status_command, but only after calling target_get_trace_status, which seems to me should be sending a packet. remote_get_trace_status's exception swallowing should be letting TARGET_CLOSE_ERROR pass through. Is that not working? I'm a bit confused because it seems like if that didn't work, we should see a "qTStatus:..." error line in the logs. So what is preventing the packet from being sent? Thanks, Pedro Alves