From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/29076] New: user_string_quoted() doesn't properly generate strings in .rodata on x86_64 machines
Date: Wed, 20 Apr 2022 14:45:52 +0000 [thread overview]
Message-ID: <bug-29076-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29076
Bug ID: 29076
Summary: user_string_quoted() doesn't properly generate strings
in .rodata on x86_64 machines
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
Target Milestone: ---
Created attachment 14073
--> https://sourceware.org/bugzilla/attachment.cgi?id=14073&action=edit
User-space and systemtap script showing issue with .rodata strings
When triaging the testsuite systemtap.syscall/syscall.exp failures I found that
strings that were stored in the .rodata section were not properly printed on
x86_64 fedora 35 machine. In their place was the pointer value passed in for
the string location.
Have a little example demonstrating the issue in x86_ro_string.tar.gz:
$ uname -a
Linux fedora 5.16.20-200.fc35.x86_64 #1 SMP PREEMPT Wed Apr 13 22:09:20 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
$ gcc -o acct2 -O2 acct2.c
$ sudo stap -c ./acct2 sys_acct.stp
[sudo] password for wcohen:
kprobe.function("__x64_sys_acct")?(0x402010)
kprobe.function("__x64_sys_acct")?("foobar")
kprobe.function("__x64_sys_acct")?(0xffffffffffffffff)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-04-20 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 14:45 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 ` 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@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).