From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15819 invoked by alias); 13 Jan 2010 04:16:36 -0000 Received: (qmail 15799 invoked by uid 22791); 13 Jan 2010 04:16:34 -0000 X-SWARE-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,BAYES_40,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 13 Jan 2010 04:16:29 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0KW600H003SCAF00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Wed, 13 Jan 2010 06:15:01 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.126.60.183]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KW600GCD3T0VV20@a-mtaout20.012.net.il>; Wed, 13 Jan 2010 06:15:00 +0200 (IST) Date: Wed, 13 Jan 2010 04:16:00 -0000 From: Eli Zaretskii Subject: Re: [PATCH] Trace file support In-reply-to: <4B4D06E8.4070601@codesourcery.com> To: Stan Shebs Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <831vhu8wt0.fsf@gnu.org> References: <4B4BD994.9070701@codesourcery.com> <838wc386hd.fsf@gnu.org> <4B4D06E8.4070601@codesourcery.com> 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/msg00323.txt.bz2 > Date: Tue, 12 Jan 2010 15:34:00 -0800 > From: Stan Shebs > CC: Stan Shebs , gdb-patches@sourceware.org > > > 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? > > > Good point - if one uses GDB to both create a trace file and read from > it, then it's effectively a private format. There is the case of the > target agent writing the file directly, but I expect that will be less > common. On the other hand, if a target stub/agent does write trace > files, then we should make some degree of stability promise (could one > get compiled into Linux kernel?), and the GDB manual is our main avenue > for describing that promise. If we went the header file route, then > there is a license issue for the file too. Then perhaps we should move the details to gdbint.texinfo, and leave only the basic stuff in gdb.texinfo.