public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: src ./ChangeLog ./parse.cxx ./stap.1.in ./stap ...
Date: Fri, 17 Aug 2007 01:54:00 -0000 [thread overview]
Message-ID: <20070817015429.17431.qmail@sourceware.org> (raw)
CVSROOT: /cvs/systemtap
Module name: src
Changes by: jistone@sourceware.org 2007-08-17 01:54:29
Modified files:
. : ChangeLog parse.cxx stap.1.in staptree.cxx
staptree.h translate.cxx
testsuite : ChangeLog
testsuite/buildok: printf.stp
testsuite/lib : stap_run.exp
Added files:
testsuite/parseko: printd01.stp printd02.stp printd03.stp
printd04.stp
testsuite/systemtap.base: print.exp print.stp
Log message:
2007-08-16 Josh Stone <joshua.i.stone@intel.com>
PR 4591
* parse.cxx (parser::parse_symbol): Tweak 'print' matching to allow
all the new variants with printd and println.
* staptree.h (struct print_format): Add fields for the new print
variants, and parse_print() to help matching.
* staptree.cxx (print_format::parse_print): New static method to
match the print variants and determine their properties.
(print_format::print): Handle the new print types.
(deep_copy_visitor::visit_print_format): Copy the new fields.
* translate.cxx (c_unparser::visit_print_format): Insert delims and
newlines where appropriate for new print functions.
* stap1.in: Document the new print functions.
testsuite/
* lib/stap_run.exp: Make sure to match the entire output, in case
there are multiple pass/fail messages.
* buildok/printf.stp: Add lines for new print variants.
* parseko/printd01.stp: Make sure that bad printd calls are handled.
* parseko/printd02.stp: Ditto.
* parseko/printd03.stp: Ditto.
* parseko/printd04.stp: Ditto.
* systemtap.base/print.stp: Try a bunch of different print calls.
* systemtap.base/print.exp: Driver for above.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/ChangeLog.diff?cvsroot=systemtap&r1=1.653&r2=1.654
http://sourceware.org/cgi-bin/cvsweb.cgi/src/parse.cxx.diff?cvsroot=systemtap&r1=1.68&r2=1.69
http://sourceware.org/cgi-bin/cvsweb.cgi/src/stap.1.in.diff?cvsroot=systemtap&r1=1.60&r2=1.61
http://sourceware.org/cgi-bin/cvsweb.cgi/src/staptree.cxx.diff?cvsroot=systemtap&r1=1.61&r2=1.62
http://sourceware.org/cgi-bin/cvsweb.cgi/src/staptree.h.diff?cvsroot=systemtap&r1=1.52&r2=1.53
http://sourceware.org/cgi-bin/cvsweb.cgi/src/translate.cxx.diff?cvsroot=systemtap&r1=1.176&r2=1.177
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/ChangeLog.diff?cvsroot=systemtap&r1=1.126&r2=1.127
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/buildok/printf.stp.diff?cvsroot=systemtap&r1=1.3&r2=1.4
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/lib/stap_run.exp.diff?cvsroot=systemtap&r1=1.8&r2=1.9
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/parseko/printd01.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/parseko/printd02.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/parseko/printd03.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/parseko/printd04.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/systemtap.base/print.exp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/testsuite/systemtap.base/print.stp.diff?cvsroot=systemtap&r1=NONE&r2=1.1
reply other threads:[~2007-08-17 1:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070817015429.17431.qmail@sourceware.org \
--to=jistone@sourceware.org \
--cc=systemtap-cvs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).