>>
>> An appears to be correctly parsed by event_read_print in
>> tools/lib/tracevent/event-parse.c . Has anyone seen this before?
>
> What kernel are you running?
>
> I just built and booted v4.11-rc8 with a v4.11-rc8 perf:
I was running an internal version. I found the bug in an internal
>>
>> An appears to be correctly parsed by event_read_print in
>> tools/lib/tracevent/event-parse.c . Has anyone seen this before?
>
> What kernel are you running?
>
> I just built and booted v4.11-rc8 with a v4.11-rc8 perf:
I was running an internal version. I found the bug in an internal
>
> But I don't see any warning when I run it with --stdio. Could you
> show me the format file of sys_enter_mmap?
I found the problem. The kernel version I was testing on fails to
initialize some fields in the tracepoint structure, so my format
looked like:
# cat
>
> But I don't see any warning when I run it with --stdio. Could you
> show me the format file of sys_enter_mmap?
I found the problem. The kernel version I was testing on fails to
initialize some fields in the tracepoint structure, so my format
looked like:
# cat
Hi,
On Fri, Apr 28, 2017 at 9:31 AM, David Carrillo-Cisneros
wrote:
> When processing tracepoint events, perf report outputs warnings about
> field not founds. The warnings are usually hidden by perf report UI
> and appear when using the --stdio option. e.g.
Yep, currently
Hi,
On Fri, Apr 28, 2017 at 9:31 AM, David Carrillo-Cisneros
wrote:
> When processing tracepoint events, perf report outputs warnings about
> field not founds. The warnings are usually hidden by perf report UI
> and appear when using the --stdio option. e.g.
Yep, currently perf report TUI hides
On Thu, 27 Apr 2017 20:51:28 -0600
David Ahern wrote:
> On 4/27/17 8:49 PM, Steven Rostedt wrote:
> > On Thu, 27 Apr 2017 20:13:43 -0600
> > David Ahern wrote:
> >
> >> On 4/27/17 7:41 PM, Steven Rostedt wrote:
> >>> On Thu, 27 Apr 2017 19:31:12 -0500
On Thu, 27 Apr 2017 20:51:28 -0600
David Ahern wrote:
> On 4/27/17 8:49 PM, Steven Rostedt wrote:
> > On Thu, 27 Apr 2017 20:13:43 -0600
> > David Ahern wrote:
> >
> >> On 4/27/17 7:41 PM, Steven Rostedt wrote:
> >>> On Thu, 27 Apr 2017 19:31:12 -0500
> >>> David Carrillo-Cisneros wrote:
On 4/27/17 8:49 PM, Steven Rostedt wrote:
> On Thu, 27 Apr 2017 20:13:43 -0600
> David Ahern wrote:
>
>> On 4/27/17 7:41 PM, Steven Rostedt wrote:
>>> On Thu, 27 Apr 2017 19:31:12 -0500
>>> David Carrillo-Cisneros wrote:
>>>
When processing
On 4/27/17 8:49 PM, Steven Rostedt wrote:
> On Thu, 27 Apr 2017 20:13:43 -0600
> David Ahern wrote:
>
>> On 4/27/17 7:41 PM, Steven Rostedt wrote:
>>> On Thu, 27 Apr 2017 19:31:12 -0500
>>> David Carrillo-Cisneros wrote:
>>>
When processing tracepoint events, perf report outputs
On Thu, 27 Apr 2017 20:13:43 -0600
David Ahern wrote:
> On 4/27/17 7:41 PM, Steven Rostedt wrote:
> > On Thu, 27 Apr 2017 19:31:12 -0500
> > David Carrillo-Cisneros wrote:
> >
> >> When processing tracepoint events, perf report outputs warnings about
>
On Thu, 27 Apr 2017 20:13:43 -0600
David Ahern wrote:
> On 4/27/17 7:41 PM, Steven Rostedt wrote:
> > On Thu, 27 Apr 2017 19:31:12 -0500
> > David Carrillo-Cisneros wrote:
> >
> >> When processing tracepoint events, perf report outputs warnings about
> >> field not founds. The warnings are
On 4/27/17 7:41 PM, Steven Rostedt wrote:
> On Thu, 27 Apr 2017 19:31:12 -0500
> David Carrillo-Cisneros wrote:
>
>> When processing tracepoint events, perf report outputs warnings about
>> field not founds. The warnings are usually hidden by perf report UI
>> and appear when
On 4/27/17 7:41 PM, Steven Rostedt wrote:
> On Thu, 27 Apr 2017 19:31:12 -0500
> David Carrillo-Cisneros wrote:
>
>> When processing tracepoint events, perf report outputs warnings about
>> field not founds. The warnings are usually hidden by perf report UI
>> and appear when using the --stdio
On Thu, 27 Apr 2017 19:31:12 -0500
David Carrillo-Cisneros wrote:
> When processing tracepoint events, perf report outputs warnings about
> field not founds. The warnings are usually hidden by perf report UI
> and appear when using the --stdio option. e.g.
>
> $ perf
On Thu, 27 Apr 2017 19:31:12 -0500
David Carrillo-Cisneros wrote:
> When processing tracepoint events, perf report outputs warnings about
> field not founds. The warnings are usually hidden by perf report UI
> and appear when using the --stdio option. e.g.
>
> $ perf record -e
When processing tracepoint events, perf report outputs warnings about
field not founds. The warnings are usually hidden by perf report UI
and appear when using the --stdio option. e.g.
$ perf record -e syscalls:sys_enter_mmap some_load
$ perf report --stdio
Warning:
When processing tracepoint events, perf report outputs warnings about
field not founds. The warnings are usually hidden by perf report UI
and appear when using the --stdio option. e.g.
$ perf record -e syscalls:sys_enter_mmap some_load
$ perf report --stdio
Warning:
18 matches
Mail list logo