From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Stone, Joshua I" <joshua.i.stone@intel.com>
Cc: systemtap@sources.redhat.com
Subject: Re: MAXACTION exceeded error while using systemtap
Date: Tue, 06 Dec 2005 20:55:00 -0000 [thread overview]
Message-ID: <20051206205537.GD9617@redhat.com> (raw)
In-Reply-To: <CBDB88BFD06F7F408399DBCF8776B3DC05C7DB06@scsmsx403.amr.corp.intel.com>
Hi -
> > See http://sourceware.org/bugzilla/show_bug.cgi?id=1866
>
> This bug was dismissed as being "behavior as designed" - but I think it
> is worth questioning the design. [...]
Bug #1866 links to #1884, which does that.
> At the very least, we should have something along the Dtrace's printa():
> [...] Bug #1121 seems applicable to this problem [...]
The print/printf routines have worked for a few weeks now. I don't
know whether Graydon intends to extend them to print arrays also. The
new print code also makes more compact the elaborate reporting
routines used thus far, and importantly, rather reduces their
statement count.
I am unsure about how to estimate the very real cost of an array-print
operator. Calling it approximately zero would make it into a
something like a DoS vector. Intuitively, it should be proportional
to the amount of output generated, so it relates to bug #1885.
- FChE
next prev parent reply other threads:[~2005-12-06 20:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 20:41 Stone, Joshua I
2005-12-06 20:55 ` Frank Ch. Eigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 17:50 Stone, Joshua I
2005-12-06 21:56 Stone, Joshua I
2005-12-06 22:11 ` Frank Ch. Eigler
2005-12-07 20:53 ` Martin Hunt
2005-12-07 21:09 ` Frank Ch. Eigler
2005-12-07 22:29 ` Martin Hunt
2005-12-07 23:07 ` Frank Ch. Eigler
2005-12-08 8:55 ` Martin Hunt
2005-12-08 12:52 ` James Dickens
2005-12-08 13:57 ` Frank Ch. Eigler
2005-12-28 19:06 ` Marcelo Tosatti
2005-12-28 20:12 ` Tom Zanussi
2005-12-28 20:38 ` Marcelo Tosatti
2005-12-28 21:13 ` Frank Ch. Eigler
2005-12-08 13:37 ` Frank Ch. Eigler
2005-12-06 16:40 Badari Pulavarty
2005-12-06 16:59 ` Frank Ch. Eigler
2005-12-07 1:10 ` Badari Pulavarty
2005-12-07 15:21 ` William Cohen
2005-12-07 16:37 ` Badari Pulavarty
2005-12-06 17:01 ` Hien Nguyen
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=20051206205537.GD9617@redhat.com \
--to=fche@redhat.com \
--cc=joshua.i.stone@intel.com \
--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).