From: "sapatel at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/24926] New: non-ascii characters not printing on stapbpf
Date: Wed, 21 Aug 2019 16:10:00 -0000 [thread overview]
Message-ID: <bug-24926-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=24926
Bug ID: 24926
Summary: non-ascii characters not printing on stapbpf
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: bpf
Assignee: systemtap at sourceware dot org
Reporter: sapatel at redhat dot com
Target Milestone: ---
All unicode characters seem to be printing on the normal Systemtap backend but,
not on stapbpf, which seems to be limited to ASCII characters only.
This can be seen with the following scripts:
'probe oneshot { print("官话") }'
'probe oneshot { print("संस्कृतम्") }'
After some discussion with serhei, it was noted that that stapbpf might be
assuming that a single character is a single byte.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-08-21 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 16:10 sapatel at redhat dot com [this message]
2019-08-21 22:05 ` [Bug bpf/24926] " me at serhei dot io
2019-08-26 18:04 ` sapatel at redhat dot com
2019-08-28 21:26 ` sapatel at redhat dot com
2019-09-03 20:07 ` sapatel 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-24926-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).