public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10690] New: need way to produce bigger procfs output
Date: Wed, 23 Sep 2009 14:17:00 -0000	[thread overview]
Message-ID: <20090923141722.10690.fche@redhat.com> (raw)

There exist uses for procfs("file").write and especially .read,
for which it is desirable for stap scripts to produce much more than
MAXSTRINGLEN bytes of output.

The probe point syntax could be extended to specify a .maxsize(NNN)
option for the probes.  Then, extra syntax of some sort would be
needed to write/read the $value variable.  Perhaps something like
this for the output side:

probe procfs("file").read.maxbuf(8192) {
  $value .= sprint("hello\n")
  $value .= sprint("more and more test\n")
}

(i.e., we'd have to special-case/optimize the concatenate-assign operator.)

I don't have a simple idea about new syntax to parse extra-long incoming
$value strings.  Maybe a special substr that takes string-references instead
of values.?

-- 
           Summary: need way to produce bigger procfs output
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=10690

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2009-09-23 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 14:17 fche at redhat dot com [this message]
2009-09-23 14:42 ` [Bug translator/10690] " przemyslaw at pawelczyk dot it
2010-01-18 20:15 ` fche at redhat dot com
2010-01-19 22:32 ` dsmith at redhat dot com
2010-01-22 20:58 ` dsmith at redhat dot com
2010-01-22 21:24 ` dsmith at redhat dot com
2010-01-26 19:46 ` dsmith at redhat dot com
2010-02-04 19:21 ` dsmith at redhat dot com
2010-02-04 19:31 ` dsmith at redhat dot com
2010-02-09  0:06 ` jistone at redhat dot com
2010-02-09 15:24 ` fche at redhat dot com
2010-02-24 17:05 ` dsmith at redhat dot com

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=20090923141722.10690.fche@redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).