From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13562 invoked by alias); 12 Mar 2013 19:45:51 -0000 Received: (qmail 13548 invoked by uid 22791); 12 Mar 2013 19:45:50 -0000 X-SWARE-Spam-Status: No, hits=-7.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 12 Mar 2013 19:45:42 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r2CJje4V009839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Mar 2013 15:45:41 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r2CJjdOi007032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 12 Mar 2013 15:45:39 -0400 From: Tom Tromey To: Yao Qi Cc: Subject: Re: [PATCH v3 09/15] Check the tstatus output on tfile target References: <1362800844-27940-1-git-send-email-yao@codesourcery.com> <1362800844-27940-10-git-send-email-yao@codesourcery.com> Date: Tue, 12 Mar 2013 19:45:00 -0000 In-Reply-To: <1362800844-27940-10-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Sat, 9 Mar 2013 11:47:18 +0800") Message-ID: <87obeoe718.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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: 2013-03/txt/msg00547.txt.bz2 >>>>> "Yao" == Yao Qi writes: Yao> +# Save trace frames to tfile. Yao> +gdb_test "tsave tstatus.tf" "Trace data saved to file 'tstatus.tf'.*" Would you mind using standard_output_file here? This is ok either way. Tom