From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-26579-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 29608 invoked by alias); 6 Jun 2019 21:30:44 -0000
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
Received: (qmail 29307 invoked by uid 48); 6 Jun 2019 21:30:26 -0000
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/24639] "next" statement not recognized by stap bpf backend
Date: Thu, 06 Jun 2019 21:30:00 -0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: systemtap
X-Bugzilla-Component: bpf
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wcohen at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: systemtap at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-24639-6586-IzyUFxUyci@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24639-6586@http.sourceware.org/bugzilla/>
References: <bug-24639-6586@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-q2/txt/msg00075.txt.bz2

https://sourceware.org/bugzilla/show_bug.cgi?id=3D24639

--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
Created attachment 11817
  --> https://sourceware.org/bugzilla/attachment.cgi?id=3D11817&action=3Ded=
it
next.stp with diagnostic prints.

ignore the previous -e example.  that isn't reproducing the problem.

It looks like changes in the values made by the kernel.function("vfs_read")
probes are not seen in the probe end. Put in the diagnostic printf in the
probes to better see what is going on.

[wcohen@localhost systemtap]$ ../install/bin/stap --bpf next.stp
BEGIN
vfs_read
value 2
status 0
end
value 2
status 2
END FAIL
[wcohen@localhost systemtap]$ ../install/bin/stap --bpf next.stp
BEGIN
vfs_read
value 0
status 0
end
value 2
status 2
END FAIL

--- Comment #4 from William Cohen <wcohen at redhat dot com> ---
Created attachment 11818
  --> https://sourceware.org/bugzilla/attachment.cgi?id=3D11818&action=3Ded=
it
next.stp with diagnostic prints.

ignore the previous -e example.  that isn't reproducing the problem.

It looks like changes in the values made by the kernel.function("vfs_read")
probes are not seen in the probe end. Put in the diagnostic printf in the
probes to better see what is going on.

[wcohen@localhost systemtap]$ ../install/bin/stap --bpf next.stp
BEGIN
vfs_read
value 2
status 0
end
value 2
status 2
END FAIL
[wcohen@localhost systemtap]$ ../install/bin/stap --bpf next.stp
BEGIN
vfs_read
value 0
status 0
end
value 2
status 2
END FAIL

--=20
You are receiving this mail because:
You are the assignee for the bug.