From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 85697 invoked by alias); 9 Oct 2018 21:17:01 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 85605 invoked by uid 89); 9 Oct 2018 21:17:00 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:2731, reporting, H*c:alternative X-HELO: mail-vs1-f44.google.com Received: from mail-vs1-f44.google.com (HELO mail-vs1-f44.google.com) (209.85.217.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 09 Oct 2018 21:16:58 +0000 Received: by mail-vs1-f44.google.com with SMTP id w1so3008186vsj.8 for ; Tue, 09 Oct 2018 14:16:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2YXJjD7dKN/U1DRGvD1GMoKIvkuUqL9WsH4H0gtqSpk=; b=cnJO5Wys7iPgiriZKNMd0pt8RViod8T9TqbyaG4hLlxKnUCjP23NWDdPSojURQXOHv /3FBjYnKtZw92BSrbYWZZeZ1RNuh5qzqSyide9ZtN7CUidCkTeXk3Iv8uIrJa+wnu3mL K+st0OFpYOXE/QxYdgC/GwdCvpSJBAd+tmtZ1MwGMthdAWBsb8ftwEI5N1cDSqW9zY/h +WYWl9AoEdZr2U9ToNCaox6SpOA+Uz6DEJm6hgcS5qulZ12rGT8yErDRry/6Pd1o3FXU +41BAfwDJMemWSR8Tb1m1PX67RqmTn6Xjpy98JK4qn0LE3BZ+UOgnLNTlVJG2tNr16AD ejLg== MIME-Version: 1.0 References: <0eeb55ca-d4e1-4db4-e601-74ca7e1151e2@redhat.com> <11b018ef2ea200e314dbce95f424eb6c@polymtl.ca> In-Reply-To: From: Bill Morgan Date: Tue, 09 Oct 2018 21:17:00 -0000 Message-ID: Subject: Re: gdb ignoring vCont supported commands To: palves@redhat.com Cc: Simon Marchi , gdb@sourceware.org Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-10/txt/msg00020.txt.bz2 On Tue, Oct 9, 2018 at 4:12 PM Pedro Alves wrote: > On 10/09/2018 09:29 PM, Bill Morgan wrote: > > On Tue, Oct 9, 2018 at 3:16 PM Simon Marchi > wrote: > > > >> On 2018-10-09 16:12, Bill Morgan wrote: > >>> I get a warning that vContSupported is unrecognized: > >>> > >>> Sending packet: > >>> > >> > $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+#df...Ack > >>> Packet received: > >>> > >> > PacketSize=3fff;QPassSignals+;qXfer:features:read+;qXfer:threads:read+;vContSupported > >>> Packet qSupported (supported-packets) is supported > >>> warning: unrecognized item "vContSupported" in "qSupported" response > >> > >> I believe you are missing the + after vContSupported. > >> > >> You are correct, I was missing the +. Thank you. > > > > So it is now recognizing the vContSupported, but it is still sending > > vCont;s > > > > Argh, I forgot that this only really works on ARM GNU/Linux. > What is your target? > Custom OS on ARM. This is what I'm reporting to GDB: Sending packet: $qXfer:features:read:target.xml:0,fff#7d...Ack Packet received: larm > > We're missing the small infrastructure change in GDB > mentioned in the discussion I linked before. > > Thanks, > Pedro Alves >