From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/29076] user_string_quoted() doesn't properly generate strings in .rodata on x86_64 machines
Date: Wed, 20 Apr 2022 14:48:05 +0000 [thread overview]
Message-ID: <bug-29076-6586-1u1HUNRLPU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29076-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29076
--- Comment #1 from William Cohen <wcohen at redhat dot com> ---
Tried the example on non-x86 platforms such as aarch64 and it gave the expected
result:
[wcohen@fedora ~]$ uname -a
Linux fedora 5.16.20-200.fc35.aarch64 #1 SMP Wed Apr 13 21:49:21 UTC 2022
aarch64 aarch64 aarch64 GNU/Linux
[wcohen@fedora ~]$ gcc -o acct2 -O2 acct2.c
[wcohen@fedora ~]$ sudo stap -c ./acct2 sys_acct.stp
warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc (GCC) 11.2.1 20220127 (Red Hat 11.2.1-9)
You are using: gcc (GCC) 11.2.1 20220401 (Red Hat 11.2.1-10)
kprobe.function("__arm64_sys_acct")?("foobar")
kprobe.function("__arm64_sys_acct")?("foobar")
kprobe.function("__arm64_sys_acct")?(0xffffffffffffffff)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-04-20 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 14:45 [Bug runtime/29076] New: " wcohen at redhat dot com
2022-04-20 14:48 ` wcohen at redhat dot com [this message]
2022-04-20 14:48 ` [Bug runtime/29076] " wcohen at redhat dot com
2022-04-20 14:48 ` fche at redhat dot com
2022-04-20 17:37 ` wcohen at redhat dot com
2022-04-20 18:02 ` fche at redhat dot com
2022-04-20 18:17 ` wcohen at redhat dot com
2022-04-21 9:33 ` mcermak at redhat dot com
2022-04-21 12:33 ` mcermak 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=bug-29076-6586-1u1HUNRLPU@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).