From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7773 invoked by alias); 12 Jan 2010 19:40:44 -0000 Received: (qmail 7753 invoked by uid 22791); 12 Jan 2010 19:40:43 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 12 Jan 2010 19:40:39 +0000 Received: from jupiter.vmware.com (mailhost5.vmware.com [10.16.68.131]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id E56D153071; Tue, 12 Jan 2010 11:40:35 -0800 (PST) Received: from [10.20.94.141] (msnyder-server.eng.vmware.com [10.20.94.141]) by jupiter.vmware.com (Postfix) with ESMTP id DAB64DC053; Tue, 12 Jan 2010 11:40:35 -0800 (PST) Message-ID: <4B4CD06B.8030703@vmware.com> Date: Tue, 12 Jan 2010 19:40:00 -0000 From: Michael Snyder User-Agent: Thunderbird 1.5.0.12 (X11/20090624) MIME-Version: 1.0 To: Eli Zaretskii CC: Stan Shebs , "gdb-patches@sourceware.org" Subject: Re: [PATCH] Trace file support References: <4B4BD994.9070701@codesourcery.com> <838wc386hd.fsf@gnu.org> In-Reply-To: <838wc386hd.fsf@gnu.org> 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-01/txt/msg00313.txt.bz2 Eli Zaretskii wrote: > >> + The trace file comes in three parts: a header, a textual description >> + section, and a trace frame section with binary data. [...] > > I wonder if we really need such a detailed description of the file's > format in the user manual. Who would need that? can we simply send > the interested reader to some header file? So long as its documented somewhere...