I have selected several trace tags and when I run the trace ( Actually there is no debug file in the kernel directory, but which mechanism will generate the necessary path? It seems that your cellphone is running a boot image, which does not support the systress . "Error opening / sys / kernel / debug / tracing / options / overwrite: There is no such file or directory (2)" This error message means ADB Damon ( ADB module is running on the device side) / sys / kernel / debug / Tracing / options / overwrite on your device's file system Systrace works on ADB and communicates with kernel though / sys / kernel / debug / tracing Sysfs nodes under. If you are not exposing these nodes to the phone for any reason, systrace will not work right now. Then you should first get a shell on your device: open ADB then browse to confirm that / sys exists in all and if / Sys / kernel / debug / tracing is present. If they are those which are less likely, then you must debug systrace.py to find out how systrace sounds that the nodes were not there otherwise you need to flash a different boot image. In which systrace support is supported, because sysfs is controlled by kernel (mostly by configuration at compile time) and init.rc, both of which are part of the boot image. You can unlock / retrieve the device by flashing a different boot image. You may also need to get fan sites like information and imagery for the image. Another option is to download the source of the kernel for your device, compile the kernel and create the boot image yourself. Linux is under GPL, so the manufacturers of your device are bound to use the source code of the special kernel to be used. -NAM DDMS ) The following output is found:
Unexpected error while collecting system trace Trace Start Marker 'TRACE:': Error opening / unable to find sys / kernel / debug / tracing / options / overwrite: such a file or directory (2) error OPI (here the error has been truncated)
No comments:
Post a Comment