From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/27030] bpf: user_long_error() leads to assertion failures in the translator
Date: Mon, 07 Dec 2020 20:29:37 +0000 [thread overview]
Message-ID: <bug-27030-6586-YR3eMOuSxM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27030-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27030
--- Comment #2 from agentzh <agentzh at gmail dot com> ---
Tried the same example on an older kernel on Fedora 28 x86_64. Same thing:
```
[agentzh@glass ~/git/systemtap.new 1 (master)]$ /opt/stap/bin/stap --bpf -c
/tmp/a.out -e 'probe process("/tmp/a.out").function("main") { println("a: ",
user_long_error(0x601020)) exit() }'
stap: staptree.h:1349: virtual update_visitor::~update_visitor(): Assertion
`values.empty()' failed.
Aborted (core dumped)
[agentzh@glass ~/git/systemtap.new 134 (master)]$ cat /proc/version
Linux version 5.0.16-100.fc28.x86_64
(mockbuild@bkernel04.phx2.fedoraproject.org) (gcc version 8.3.1 20190223 (Red
Hat 8.3.1-2) (GCC)) #1 SMP Tue May 14 18:22:28 UTC 2019
[agentzh@glass ~/git/systemtap.new 0 (master)]$ /opt/stap/bin/stap -V
Systemtap translator/driver (version 4.5/0.177, commit
release-4.4-24-g3e0d449fe427 + changes)
Copyright (C) 2005-2020 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.32 ... 5.10.0-rc
enabled features: BOOST_STRING_REF DYNINST BPF LIBSQLITE3 LIBXML2 NLS READLINE
```
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-12-07 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 20:13 [Bug bpf/27030] New: " agentzh at gmail dot com
2020-12-07 20:27 ` [Bug bpf/27030] " agentzh at gmail dot com
2020-12-07 20:29 ` agentzh at gmail dot com [this message]
2021-03-01 15:31 ` 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-27030-6586-YR3eMOuSxM@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).