From: Stan Shebs <stan@codesourcery.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Trace file support
Date: Fri, 15 Jan 2010 22:44:00 -0000 [thread overview]
Message-ID: <4B50EFDA.3050108@codesourcery.com> (raw)
In-Reply-To: <4B4BD994.9070701@codesourcery.com>
Stan Shebs wrote:
> This patch adds support for trace files, which are simply dumps of a
> target's tracepoints and trace buffer. In addition to the new "tsave"
> command to create a trace file, there is a new target "tfile" that
> opens a trace file and then lets you do tfind and then print any data
> that was collected, just as for you would do for a live target.
I've just committed all this. Just a few minor changes from the posted
version; a NEWS item, a gdbtk tweak, testsuite addition, and fixes for
bugs exposed by testsuite :-) . The testsuite bit is notable in that it
supposedly can run anywhere, irrespective of architecture and existence
live tracing support, by having the test program manually synthesize a
trace file. Be sure to let me know if I'm wrong about its portability!
Stan
prev parent reply other threads:[~2010-01-15 22:44 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
2010-01-13 18:44 ` Stan Shebs
2010-01-15 22:44 ` Stan Shebs [this message]
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=4B50EFDA.3050108@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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