From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2610] New: @ops on empty scalar statistics aggregates
Date: Wed, 26 Apr 2006 22:10:00 -0000 [thread overview]
Message-ID: <20060426221013.2610.fche@redhat.com> (raw)
For arrays of aggregates, accessing a nonexistent value results in an error:
a[2] <<< 2; @avg(a[3])
This is intentional, since @avg is considered undefined for a zero-element
list. However, for scalars, we don't enforce this same thing:
@avg(b) ; @max(b)
may spit out a generic division-by-zero error or a sentinel "0" value.
It should be made consistent with the vector-of-aggregates case, so that
only @count() is valid on an empty aggregate scalar.
--
Summary: @ops on empty scalar statistics aggregates
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=2610
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2006-04-26 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 22:10 fche at redhat dot com [this message]
2006-05-01 13:50 ` [Bug translator/2610] " fche 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=20060426221013.2610.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).