From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12869 invoked by alias); 16 Oct 2014 17:03:48 -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 12794 invoked by uid 89); 16 Oct 2014 17:03:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,NO_DNS_FOR_FROM,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: mailuogwdur.emc.com Received: from mailuogwdur.emc.com (HELO mailuogwdur.emc.com) (128.221.224.79) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Thu, 16 Oct 2014 17:03:46 +0000 Received: from maildlpprd51.lss.emc.com (maildlpprd51.lss.emc.com [10.106.48.155]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9GH3hPZ022136 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 16 Oct 2014 13:03:44 -0400 X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s9GH3hPZ022136 X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s9GH3hPZ022136 Received: from mailsyshubprd06.lss.emc.com (mailsyshubprd06.lss.emc.com [10.253.24.24]) by maildlpprd51.lss.emc.com (RSA Interceptor) for ; Thu, 16 Oct 2014 13:03:04 -0400 Received: from usendtaylorx2l.lss.emc.com (usendtaylorx2l.lss.emc.com [10.243.10.188]) by mailsyshubprd06.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s9GH3VLT027932 for ; Thu, 16 Oct 2014 13:03:32 -0400 Received: by usendtaylorx2l.lss.emc.com (Postfix, from userid 26043) id 315475D5BAC; Thu, 16 Oct 2014 13:03:30 -0400 (EDT) Received: from usendtaylorx2l (localhost [127.0.0.1]) by usendtaylorx2l.lss.emc.com (Postfix) with ESMTP id 8B44D5D5B8B for ; Thu, 16 Oct 2014 13:03:30 -0400 (EDT) To: "gdb@sourceware.org" Subject: Re: possible QTFrame enhancement In-reply-to: <4250.1411074396@usendtaylorx2l> References: <4250.1411074396@usendtaylorx2l> Comments: In-reply-to David Taylor message dated "Thu, 18 Sep 2014 17:06:36 -0400." Date: Thu, 16 Oct 2014 17:03:00 -0000 Message-ID: <13378.1413479010@usendtaylorx2l> From: David Taylor X-RSA-Classifications: public X-Sentrion-Hostname: mailuogwprd52.lss.emc.com X-SW-Source: 2014-10/txt/msg00049.txt.bz2 In mid September I asked about a possible QTFrame / tfind enhancement. That message generated zero responses. I'm hoping to get back in a day or two to our effort of adding the setting of memory and registers at tracepoints. (It's more than half done; but, before I finished I got yanked onto another project.) I won't be working on implementing these proposed QTFrame / tframe enhancements until that (and possibly some other stuff) is done. For the remote protocol there currently several variants of the QTFrame message: QTFrame:n QTFrame:pc:addr QTFrame:tdp:t QTFrame:range:start:end QTFrame:outside:start:end And variants of the tfind command: tfind end tfind line tfind none tfind outside tfind pc tfind range tfind start tfind tracepoint We (EMC) have a developer who runs trace experiments that generate *LOTS* of tracepoint frames -- possibly 100,000 or more! He then likes to find an anomaly and search *BACKWARDS* to find where things first started going bad. Other than the first QTFrame variant above -- which does no searching -- all of the above QTFrame variants search *FORWARDS* from the current tracepoint frame. I would like to propose that tfind be modified from tfind to tfind [ -r | --reverse] and that the QTFrame remote protocol message have an optional `-' before the first `:' to indicate reverse: QTFrame-:n QTFrame-:pc:addr QTFrame-:tdp:t QTFrame-:range:start:end QTFrame-:outside:start:end And for qSupported I propose: QTFrameReverse+ QTFrameReverse- to indicate whether it is supported or not. Does this proposal seem reasonable to people? Would an implementation of this stand a resonable chance of being accepted back? Thanks. David