From: Arun Kalyanasundaram <arunkaly@google.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arun Kalyanasundaram <arunkaly@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S . Miller" <davem@davemloft.net>,
SeongJae Park <sj38.park@gmail.com>,
davidcc@google.com, Stephane Eranian <eranian@google.com>,
Arun Kalyanasundaram <arunkalys@gmail.com>
Subject: [PATCH 0/1] perf script python: Garbled text in tracepoint fields
Date: Fri, 11 Aug 2017 13:38:08 -0700 [thread overview]
Message-ID: <20170811203809.120130-1-arunkaly@google.com> (raw)
The string stored in some of the fields of tracepoint handlers has unused non-ascii characters beyond the first null ternimating character. As a result the call to is_printable_array fails and the python handlers receive the entire field as a byte array instead of just the subset of chars that represent the string.
This change calls is_printable_array with the correct length of the string instead of the entire field size.
Bug report: lkml/2017/7/18/228
Arun Kalyanasundaram (1):
perf script python: Garbled text in tracepoint fields
tools/perf/util/scripting-engines/trace-event-python.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
--
2.14.0.434.g98096fd7a8-goog
next reply other threads:[~2017-08-11 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 20:38 Arun Kalyanasundaram [this message]
2017-08-11 20:38 ` [PATCH 1/1] " Arun Kalyanasundaram
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=20170811203809.120130-1-arunkaly@google.com \
--to=arunkaly@google.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=arunkalys@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sj38.park@gmail.com \
/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
all inboxes | Powered by JetHome®