From: Chris Phlipot <cphlipot0@gmail.com>
To: adrian.hunter@intel.com, acme@kernel.org, peterz@infradead.org,
mingo@redhat.com
Cc: linux-kernel@vger.kernel.org, Chris Phlipot <cphlipot0@gmail.com>
Subject: [PATCH 2/2] perf script: fix incorrect python db-export error message
Date: Sat, 7 May 2016 02:17:00 -0700 [thread overview]
Message-ID: <1462612620-25008-2-git-send-email-cphlipot0@gmail.com> (raw)
In-Reply-To: <1462612620-25008-1-git-send-email-cphlipot0@gmail.com>
fix the error message printed when attempting and failing to create the
call path root incorrectly references the call return process.
this change fixes the message to properly reference the failure to create
the call path root.
Signed-off-by: Chris Phlipot <cphlipot0@gmail.com>
---
tools/perf/util/scripting-engines/trace-event-python.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/scripting-engines/trace-event-python.c b/tools/perf/util/scripting-engines/trace-event-python.c
index 091bce6..1546b74 100644
--- a/tools/perf/util/scripting-engines/trace-event-python.c
+++ b/tools/perf/util/scripting-engines/trace-event-python.c
@@ -1062,7 +1062,7 @@ static void set_table_handlers(struct tables *tables)
tables->dbe.cpr = call_path_root__new();
if (!tables->dbe.cpr)
- Py_FatalError("failed to create calls processor");
+ Py_FatalError("failed to create call path root");
}
tables->db_export_mode = true;
--
2.7.4
next prev parent reply other threads:[~2016-05-07 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 9:16 [PATCH 1/2] perf tools: fix handling of zero-length symbols Chris Phlipot
2016-05-07 9:17 ` Chris Phlipot [this message]
2016-05-10 20:31 ` [tip:perf/core] perf script: Fix incorrect python db-export error message tip-bot for Chris Phlipot
2016-05-09 17:06 ` [PATCH 1/2] perf tools: fix handling of zero-length symbols Arnaldo Carvalho de Melo
2016-05-09 17:51 ` Chris Phlipot
2016-05-10 20:33 ` [tip:perf/core] perf symbols: Fix " tip-bot for Chris Phlipot
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=1462612620-25008-2-git-send-email-cphlipot0@gmail.com \
--to=cphlipot0@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 NNTP newsgroup(s).