From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id BB8523858407; Fri, 24 Sep 2021 08:46:04 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BB8523858407
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/28378] semantic error: process return probes not
 available [man error::inode-uprobes]
Date: Fri, 24 Sep 2021 08:46:04 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: systemtap
X-Bugzilla-Component: runtime
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mark at klomp dot org
X-Bugzilla-Status: UNCONFIRMED
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: 
Message-ID: <bug-28378-6586-NpAGZsWkqF@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28378-6586@http.sourceware.org/bugzilla/>
References: <bug-28378-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-BeenThere: systemtap@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Systemtap mailing list <systemtap.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/systemtap>,
 <mailto:systemtap-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/systemtap/>
List-Help: <mailto:systemtap-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/systemtap>,
 <mailto:systemtap-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Sep 2021 08:46:04 -0000

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

--- Comment #6 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Nylon Chen from comment #5)
> but my stap has other error
> "semantic error: while processing probe tp_syscall.read.return from:
> nd_syscall.read.return from: syscall.read.return from: syscall.read.retur=
n"

Right, but that seems a totally other issue than you originally reported.
If you were using syscall probes then you really should have added that to =
the
original report. I suspect other issues you are seeing might also come from=
 not
providing the full script you are using.

Might I again suggest you upgrade your system to something more modern and/=
or
contact Ubuntu support about the kernel/systemtap combination they are ship=
ping
to make sure they are compatible.

> I try to reduce this stap script
>=20
> ```
> ...
>=20
> probe syscall.write { write_fds[tid()] =3D fd }
>=20
> probe syscall.write.return {
>   p =3D pid()
>   // Get fd even if non-dwarf syscall return probe.
>   fd =3D write_fds[tid()]
>   delete write_fds[tid()]
>   bytes =3D retval
>   time =3D gettimeofday_us() - @entry(gettimeofday_us())
>   if (bytes > 0)
>     filewrite[p, fd] <<< bytes
>   time_io[p, fd] <<< time
> }
>=20
> ...
> ```
>=20
> the error message point out the problem is "syscall.xxx.return"
>=20
> I try to comment (/**/) it, and the compiler's result is ok
>=20
> I just curious about this result.

Right, since your systemtap/kernel doesn't support return probes you cannot=
 use
@entry in your script. Since you already have an syscall entry probe I sugg=
est
to record the time in the same way you record the write_fds.

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