From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7693 invoked by alias); 10 Apr 2010 00:11:05 -0000 Received: (qmail 7677 invoked by uid 22791); 10 Apr 2010 00:11:05 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-1.vmware.com (HELO smtp-outbound-1.vmware.com) (65.115.85.69) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 10 Apr 2010 00:10:58 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 0C77813023; Fri, 9 Apr 2010 17:10:56 -0700 (PDT) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost4.vmware.com (Postfix) with ESMTP id 0042CC9A0C; Fri, 9 Apr 2010 17:10:55 -0700 (PDT) Message-ID: <4BBFC20F.8040802@vmware.com> Date: Sat, 10 Apr 2010 00:11:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20100311) MIME-Version: 1.0 To: Stan Shebs CC: "gdb-patches@sourceware.org" Subject: Re: [PATCH] One more for MI trace status References: <4BBF9429.4090804@codesourcery.com> In-Reply-To: <4BBF9429.4090804@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 X-SW-Source: 2010-04/txt/msg00290.txt.bz2 Stan Shebs wrote: > There is one more field that's been overlooked for trace_status_mi - > total frames created. (More trace status additions are coming, perhaps > we should revisit the idea of sharing CLI and MI versions...) > > I note that MI commands for tracing need testsuite. But there's a > conundrum; should tests go in gdb.mi or gdb.trace? :-) I would say in gdb.mi. Just as tests for MI- reverse debugging should go in mi rather than in gdb.reverse.