From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23480 invoked by alias); 1 Nov 2016 21:15:20 -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 23420 invoked by uid 89); 1 Nov 2016 21:15:13 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=Trunk, flavors, Hx-languages-length:1356, H*M:sk:94eb2c0 X-HELO: mail-pa0-f73.google.com Received: from mail-pa0-f73.google.com (HELO mail-pa0-f73.google.com) (209.85.220.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 01 Nov 2016 21:15:11 +0000 Received: by mail-pa0-f73.google.com with SMTP id yw6so2247488pac.1 for ; Tue, 01 Nov 2016 14:15:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:message-id:date:subject:from:to; bh=beeGbdOaf6qDzh6Kwa5eETI5GyUTBQ1pRFhY1LLEWqs=; b=S+LhaAU2V3SeUuA4SoAD00Asex3vhB5vn9HNTT12GcZSsbT3Fj8ObJfmiipzUhttnk oJa1ew5mGKzZfVc2ijtTHr3cZ3w1CTrCfjSeI6X+ieI2RuN4THLZ5qc0+n3V3h02/QXx LNQOdJ7JNRTs83A73mhwWgGs7IXs5KTCrbzh2UltigYaBRSWdHoyOEd85EKsdc4/vV2c g60/+iCiN0+9CG//Fv2rbJ71QZLHgKCfQfkNqzDwPFMFjbl0IDkvi6APY131fXnozuw/ yDY2Z+9drH+L2vbXAk2RRqmkvQyhYzH8WN2VMtHqP6O5paUB5HrSmp7znEFKTAMxettg hIog== X-Gm-Message-State: ABUngvc3EPwB8WhIpdyJFuvUbBtdaHgPIBgNhv0ZBVgUbT2yKkrmU1HgkZsA/YlzEgL3I8cX3IaSwNSbr3hDWWfN1lAhIY/dQrrTP1u06PnJRwtmXWXuwhUtolV3GAEwNaVUHTaK2X4mpvjoYPi5Le6iz1oq4zFCi/NRpfYlAgA= MIME-Version: 1.0 X-Received: by 10.98.98.135 with SMTP id w129mr27541pfb.28.1478034906807; Tue, 01 Nov 2016 14:15:06 -0700 (PDT) Message-ID: <94eb2c043598965907054043d1f7@google.com> Date: Tue, 01 Nov 2016 21:15:00 -0000 Subject: vCont: optional packet or not? From: Doug Evans To: gdb@sourceware.org, palves@redhat.com Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes X-IsSubscribed: yes X-SW-Source: 2016-11/txt/msg00000.txt.bz2 Hi. Two main questions/issues: 1) In non-stop mode is vCont a required or optional packet a stub needs to provide? 2) Trunk seems to have regressed (could be wrong) with respect to first checking whether vCont is supported before using it. In 7.12 it seems optional. I don't remember exactly, but the 7.12 code does do some checking whether vCont is supported before sending vCont packets. Things are further confusing :-( :-( :-( because there's also vContSupported which the docs say indicates whether vCont? is supported, not whether vCont is supported. [The name could be a teensy bit better ...] vCont? will tell gdb whether vCont is supported (including what flavors (c,C,s,S,t,...), but gdb only uses this to check whether vCont;[sS] (singlestepping) is supported, not whether e.g., vCont;[cC] (continue) is supported. So where's the check for whether vCont;[cC] is supported? Things have changed from 7.12, I think, in trunk. I'm seeing gdb issue vCont;c packets and complaining about bad replies from my stub, but it has never asked or even checked whether the packet is supported. [e.g., remote_commit_resume just blindly sends vCont.] What's the story here? If someone can describe how things are intended to work, I'll volunteer to fix/enhance the remote protocol spec in the docs. [Or you can directly.]