Bug 9838

Summary: perf fails on eclipse, sending a weird command remotely to qemu
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: Humberto Ibarra <humberto.ibarra.lopez>
Component: eclipse-pluginAssignee: Tim Orling <tim.orling>
Status: CLOSED WONTFIX QA Contact: Libertad <libertad.gonzalez.de.la.cruz>
Severity: normal    
Priority: Medium CC: brian.avery, ioanax.grigoropol, sgw, yp.ep.watcher, yp.watcher
Version: 2.2   
Target Milestone: 2.2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Humberto Ibarra 2016-06-28 16:57:41 UTC
I have a qemu instance running and perf appears to be in order there.Even so, when issuing perf from eclipse (YoctoProjectTools>perf) no info is displayed. The following is the output from eclipse console view:


Last login: Tue Jun 28 16:15:43 2016 from 192.168.7.1
export TERM=vt100;cd; perf
root@qemux86:~# 1;97R

The command ends there. Not sure what this "1;97R" means, but it seems to be input sent by eclipse and not output returned from qemu. Actually the eclipse-poky code has the perf init command as "cd; perf\r", not sure if the carriage return is translated here oddly.

The connection is fine since I could still run commands from the terminal opened by eclipse:

-sh: 1: command not found
-sh: 97R: command not found
root@qemux86:~# perf

 usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS]

 The most commonly used perf commands are:
   annotate        Read perf.data (created by perf record) and display annotated code
   archive         Create archive with object files with build-ids found in perf.data file
   bench           General framework for benchmark suites
   buildid-cache   Manage build-id cache.
   buildid-list    List the buildids in a perf.data file
   data            Data file related processing
   diff            Read perf.data files and display the differential profile
   evlist          List the event names in a perf.data file
   inject          Filter to augment the events stream with additional information
   kmem            Tool to trace/measure kernel memory properties
   kvm             Tool to trace/measure kvm guest os
   list            List all symbolic event types
   lock            Analyze lock events
   mem             Profile memory accesses
   record          Run a command and record its profile into perf.data
   report          Read perf.data (created by perf record) and display the profile
   sched           Tool to trace/measure scheduler properties (latencies)
   script          Read perf.data (created by perf record) and display trace output
   stat            Run a command and gather performance counter statistics
   test            Runs sanity tests.
   timechart       Tool to visualize total system behavior during a workload
   top             System profiling tool.
   trace           strace inspired tool
   probe           Define new dynamic tracepoints

 See 'perf help COMMAND' for more information on a specific command.

root@qemux86:~#
Comment 1 Humberto Ibarra 2016-06-28 19:08:47 UTC
Similar issue with latencytop

Last login: Tue Jun 28 19:09:22 2016 from 192.168.7.1
export TERM=xterm;export PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin; cd; latencytop
root@qemux86:~# 2;99R
Comment 2 brian avery 2016-09-27 17:31:37 UTC
Yocto tools are no longer being actively supported. We plan to replace most, but not all, of the functionality in the CROPS Eclipse plugin by leveraging Linux Tools, provided by Eclipse.
Comment 3 Armin Kuster 2019-05-23 15:06:57 UTC
closing