From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [PATCH][RFC] tracing: Use class->reg() for all registering of events
Date: Wed, 9 Jun 2010 09:35:30 -0300 [thread overview]
Message-ID: <20100609123530.GB9471@ghostprotocols.net> (raw)
In-Reply-To: <20100609122338.GA9471@ghostprotocols.net>
Em Wed, Jun 09, 2010 at 09:23:38AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Jun 09, 2010 at 09:02:24AM -0300, Arnaldo Carvalho de Melo escreveu:
> > > On Wed, 2010-06-09 at 17:17 +0530, Srikar Dronamraju wrote:
> > > > When ran gdb on the core, it showed me that it was dumping in
> > > > /usr/lib64/libnewt.so.0.52. in newtScaleSet function.
> > > > My newt lib was of version : newt-0.52.2-15
>
> Can you please provide a backtrace? I think I know what the problem is,
> but I'm not managing to reproduce it here.
>
> > > > I am now able to workaround the problem by uninstalling newt-devel.
If you can reinstall it and then try with the following patch, that is
the minimal for .35, I'd appreciate,
Thanks,
- Arnaldo
diff --git a/tools/perf/util/newt.c b/tools/perf/util/newt.c
index cf182ca..059b772 100644
--- a/tools/perf/util/newt.c
+++ b/tools/perf/util/newt.c
@@ -43,6 +43,12 @@ struct ui_progress *ui_progress__new(const char *title, u64 total)
if (self != NULL) {
int cols;
+ /*
+ * FIXME: We should have a per UI backend way of showing
+ * progress, stdio will just show a percentage as NN%, etc.
+ */
+ if (use_browser <= 0)
+ return self;
newtGetScreenSize(&cols, NULL);
cols -= 4;
newtCenteredWindow(cols, 1, title);
@@ -67,14 +73,18 @@ out_free_self:
void ui_progress__update(struct ui_progress *self, u64 curr)
{
+ if (use_browser <= 0)
+ return;
newtScaleSet(self->scale, curr);
newtRefresh();
}
void ui_progress__delete(struct ui_progress *self)
{
- newtFormDestroy(self->form);
- newtPopWindow();
+ if (use_browser > 0) {
+ newtFormDestroy(self->form);
+ newtPopWindow();
+ }
free(self);
}
next prev parent reply other threads:[~2010-06-09 12:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 15:33 [PATCH][RFC] tracing: Use class->reg() for all registering of events Steven Rostedt
2010-06-08 15:57 ` Peter Zijlstra
2010-06-08 17:35 ` Srikar Dronamraju
2010-06-08 19:10 ` Steven Rostedt
2010-06-08 19:11 ` Steven Rostedt
2010-06-09 5:05 ` Srikar Dronamraju
2010-06-09 6:32 ` Peter Zijlstra
2010-06-09 11:47 ` Srikar Dronamraju
2010-06-09 11:53 ` Peter Zijlstra
2010-06-09 12:02 ` Arnaldo Carvalho de Melo
2010-06-09 12:23 ` Arnaldo Carvalho de Melo
2010-06-09 12:35 ` Arnaldo Carvalho de Melo [this message]
2010-06-10 8:27 ` Srikar Dronamraju
2010-06-10 14:07 ` Arnaldo Carvalho de Melo
2010-06-10 14:52 ` Steven Rostedt
2010-06-10 15:12 ` Srikar Dronamraju
2010-06-10 18:41 ` Steven Rostedt
2010-06-10 20:36 ` Peter Zijlstra
2010-06-10 20:41 ` Steven Rostedt
2010-06-08 18:36 ` Peter Zijlstra
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=20100609123530.GB9471@ghostprotocols.net \
--to=acme@infradead.org \
--cc=ananth@in.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.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