From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] perf trace: Fix crash on RHEL6
Date: Thu, 05 Dec 2013 07:27:52 -0700 [thread overview]
Message-ID: <52A08D68.5020701@gmail.com> (raw)
In-Reply-To: <20131205130924.GA10333@ghostprotocols.net>
On 12/5/13, 6:09 AM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Dec 04, 2013 at 07:41:40PM -0700, David Ahern escreveu:
>> Signed-off-by: David Ahern <dsahern@gmail.com>
>
> What would make no fields to be present if tp_format is not NULL, i.e.
> if the /format file was successfully parsed?
Sometimes it is not successfully parsed. I see failed to parse messages,
so most likely the root cause. I was posting this one and the first one
hoping you could take a look at RHEL6 problems. I think it is mostly an
old kernel thing.
David
next prev parent reply other threads:[~2013-12-05 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 2:41 [PATCH 0/4] perf trace fixes David Ahern
2013-12-05 2:41 ` [PATCH 1/4] perf trace: Add support for syscalls vs raw_syscalls David Ahern
2013-12-11 11:03 ` [tip:perf/core] " tip-bot for David Ahern
2013-12-05 2:41 ` [PATCH 2/4] perf trace: Fix crash on RHEL6 David Ahern
2013-12-05 13:09 ` Arnaldo Carvalho de Melo
2013-12-05 14:27 ` David Ahern [this message]
2013-12-05 14:47 ` Arnaldo Carvalho de Melo
2013-12-05 2:41 ` [PATCH 3/4] perf trace: Fix summary percentage when processing files David Ahern
2013-12-11 11:03 ` [tip:perf/core] " tip-bot for David Ahern
2013-12-05 2:41 ` [PATCH 4/4] perf trace: Add option to specify machine type David Ahern
2013-12-05 13:50 ` Arnaldo Carvalho de Melo
2013-12-05 14:33 ` David Ahern
2013-12-05 14:49 ` Arnaldo Carvalho de Melo
2013-12-05 4:04 ` [PATCH 0/4] perf trace fixes David Ahern
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=52A08D68.5020701@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.