From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/23478] bpf: multi-key associative arrays
Date: Tue, 28 May 2019 13:51:00 -0000 [thread overview]
Message-ID: <bug-23478-6586-aejxRMQkRO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23478-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23478
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wcohen at redhat dot com
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
This would also be useful for the @entry support. A number of the systemtap
examples fail like in the following way:
TEST
PWD=/home/wcohen/systemtap_write/systemtap/testsuite/systemtap.examples/memory
meta taglines 'test_check: stap -p4 overcommit.stp' tag 'test_check' value
'stap -p4 overcommit.stp'
attempting command stap --bpf -p4 overcommit.stp
OUT semantic error: unhandled multi-dimensional array: identifier '$pages' at
overcommit.stp:6:40
source: execname(), pid(), @entry($pages))
^
Pass 4: compilation failed. [man error::pass4]
child process exited abnormally
RC 1
FAIL: systemtap.examples/memory/overcommit build
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-05-28 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 19:04 [Bug bpf/23478] New: " me at serhei dot io
2019-05-28 13:51 ` wcohen at redhat dot com [this message]
2019-08-20 20:49 ` [Bug bpf/23478] " wcohen at redhat dot com
2021-08-30 15:21 ` me at serhei dot io
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=bug-23478-6586-aejxRMQkRO@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).