Re: [PATCH] perf:util:dso: Using O_CLOEXEC in do_open

On Mon, Jan 15, 2018 at 01:04:48PM +0800, Wang YanQing wrote: > I meet strange behavior with below commands on my gentoo box: > 1:perf kmem record > 2:CTRL-C to stop 1 > 3:perf report > 4:"Enter", "Enter", "Run scripts for all samples", > "event_analyzing_sample". > > Then perf report: > " > No

Re: [PATCH] perf:util:dso: Using O_CLOEXEC in do_open

On Mon, Jan 15, 2018 at 10:45:06AM +0100, Jiri Olsa wrote: > On Mon, Jan 15, 2018 at 01:04:48PM +0800, Wang YanQing wrote: > > I meet strange behavior with below commands on my gentoo box: > > 1:perf kmem record > > 2:CTRL-C to stop 1 > > 3:perf report > > 4:"Enter", "Enter", "Run scripts for all s

Re: [PATCH] perf:util:dso: Using O_CLOEXEC in do_open

On Mon, Jan 15, 2018 at 01:04:48PM +0800, Wang YanQing wrote: > I meet strange behavior with below commands on my gentoo box: > 1:perf kmem record > 2:CTRL-C to stop 1 > 3:perf report > 4:"Enter", "Enter", "Run scripts for all samples", > "event_analyzing_sample". > > Then perf report: > " > No

[PATCH] perf:util:dso: Using O_CLOEXEC in do_open

I meet strange behavior with below commands on my gentoo box: 1:perf kmem record 2:CTRL-C to stop 1 3:perf report 4:"Enter", "Enter", "Run scripts for all samples", "event_analyzing_sample". Then perf report: " No kallsyms or vmlinux with build-id was found /lib/modules/4.10.0+/build/vmlinu