Re: [PATCH] Trace file support

[Eli Zaretskii <eliz at gnu dot org>]

> Date: Tue, 12 Jan 2010 15:34:00 -0800
> From: Stan Shebs <stan@codesourcery.com>
> CC: Stan Shebs <stan@codesourcery.com>, 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.