From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Trace file support
Date: Wed, 13 Jan 2010 04:16:00 -0000 [thread overview]
Message-ID: <831vhu8wt0.fsf@gnu.org> (raw)
In-Reply-To: <4B4D06E8.4070601@codesourcery.com>
> 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.
next prev parent reply other threads:[~2010-01-13 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 2:08 Stan Shebs
2010-01-12 19:31 ` Eli Zaretskii
2010-01-12 19:40 ` Michael Snyder
2010-01-12 23:34 ` Stan Shebs
2010-01-13 4:16 ` Eli Zaretskii [this message]
2010-01-13 18:44 ` Stan Shebs
2010-01-15 22:44 ` Stan Shebs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831vhu8wt0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox