HarmonyOS 鸿蒙Next 使用本地模拟器跑官方示例,Log日志不断输出错误

05-14 19:16:48.643 15681-15773/? E 02F10/HwSecurityServer: ConnectRemoteServiceManager:fail to bind remote service: com.huawei.deviceauth.CleanRedundancyService and retry  
05-14 19:16:49.670 15681-15773/? E 02F10/HwSecurityServer: ConnectRemoteServiceManager:fail to bind remote service: com.huawei.deviceauth.CleanRedundancyService and retry  

05-07 17:13:39.515 341-341/? F libc/ : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xc in tid 341 (cust_init), pid 341 (cust_init)  
05-07 17:13:39.653 346-346/? F DEBUG/ : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***  
05-07 17:13:39.653 346-346/? F DEBUG/ : Build fingerprint: 'HUAWEI/JAD-AN00/HWFCO:12/HUAWEIJAD-AN00/3.1.0.155SP50C00:userdebug/dev-keys'  
05-07 17:13:39.653 346-346/? F DEBUG/ : Revision: '0'  
05-07 17:13:39.653 346-346/? F DEBUG/ : ABI: 'x86_64'  
05-07 17:13:39.653 346-346/? F DEBUG/ : Timestamp: 2024-05-07 17:13:39.609590659+0800  
05-07 17:13:39.653 346-346/? F DEBUG/ : Process uptime: 0s  
05-07 17:13:39.653 346-346/? F DEBUG/ : Cmdline: /system/bin/cust_init  
05-07 17:13:39.653 346-346/? F DEBUG/ : pid: 341, tid: 341, name: cust_init &gt;&gt;&gt; /system/bin/cust_init &lt;&lt;&lt;  
05-07 17:13:39.654 346-346/? F DEBUG/ : uid: 0  
05-07 17:13:39.654 346-346/? F DEBUG/ : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xc  
05-07 17:13:39.654 346-346/? F DEBUG/ : Cause: null pointer dereference  
05-07 17:13:39.654 346-346/? F DEBUG/ : rax 0000000000000000 rbx 0000000000000000 rcx 000000000000000c rdx 0000000000000000  
05-07 17:13:39.654 346-346/? F DEBUG/ : r8 0000000000000007 r9 0000000000000000 r10 000056acc4557354 r11 000056acc452e22a  
05-07 17:13:39.654 346-346/? F DEBUG/ : r12 0000000000000007 r13 0000000000000000 r14 000056acc452e22a r15 0000000000000400  
05-07 17:13:39.654 346-346/? F DEBUG/ : rdi 000000000000000c rsi 0000000000000073  
05-07 17:13:39.654 346-346/? F DEBUG/ : rbp 000056acc45577f0 rsp 00007ffd2f2b7bd8 rip 00007d13642db621  
05-07 17:13:39.655 346-346/? F DEBUG/ : backtrace:  
05-07 17:13:39.655 346-346/? F DEBUG/ : #00 pc 0000000000095621 /apex/com.android.runtime/lib64/bionic/libc.so (strlen+17) (BuildId: 2de37b8aa6e96dd64a6cfa51bd78ae6e)  
05-07 17:13:39.655 346-346/? F DEBUG/ : #01 pc 0000000000094aae /system/bin/cust_init (SecVsnprintfImpl+3710) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)  
05-07 17:13:39.655 346-346/? F DEBUG/ : #02 pc 0000000000093b0d /system/bin/cust_init (vsnprintf_s+61) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)  
05-07 17:13:39.655 346-346/? F DEBUG/ : #03 pc 00000000000482bc /system/bin/cust_init (RecoveryPrint+460) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)  
05-07 17:13:39.655 346-346/? F DEBUG/ : #04 pc 0000000000049487 /system/bin/cust_init (HwRecoverySymlinkFile+327) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)  
05-07 17:13:39.655 346-346/? F DEBUG/ : #05 pc 000000000003d406 /system/bin/cust_init (SymlinkCust+454) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)  
05-07 17:13:39.655 346-346/? F DEBUG/ : #06 pc 000000000003e579 /system/bin/cust_init (DefaultCust+905) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)  
05-07 17:13:39.655 346-346/? F DEBUG/ : #07 pc 000000000003ae3d /system/bin/cust_init (main+205) (BuildId: 5fe142fe5d6bb44ad9476509b4ec8734)  
05-07 17:13:39.655 346-346/? F DEBUG/ : #08 pc 0000000000090cf9 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+89) (BuildId: 2de37b8aa6e96dd64a6cfa51bd78ae6e)  

05-07 17:18:23.585 12113-12113/? F linker/ : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.usb@1.0-service": library "android.hardware.usb@1.0.so" not found: needed by main executable  

05-07 17:19:24.956 13774-13774/? E AndroidRuntime/ : FATAL EXCEPTION: main  
05-07 17:19:24.956 13774-13774/? E AndroidRuntime/ : Process: com.android.systemui, PID: 13774  
05-07 17:19:24.956 13774-13774/? E AndroidRuntime/ : DeadSystemException: The system died; earlier logs will point to the root cause  
05-07 17:19:25.257 13891-14177/? E AndroidRuntime/ : FATAL EXCEPTION: pool-3-thread-3  
05-07 17:19:25.257 13891-14177/? E AndroidRuntime/ : Process: com.android.permissioncontroller, PID: 13891  
05-07 17:19:25.257 13891-14177/? E AndroidRuntime/ : DeadSystemException: The system died; earlier logs will point to the root cause  

05-07 17:20:37.249 15189-15189/? F linker/ : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.usb@1.0-service": library "android.hardware.usb@1.0.so" not found: needed by main executable  

05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : FATAL EXCEPTION: main  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : Process: com.huawei.hiai, PID: 18417  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : java.lang.RuntimeException: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:125)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at android.os.Handler.dispatchMessage(Handler.java:117)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at android.os.Looper.loopOnce(Looper.java:205)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at android.os.Looper.loop(Looper.java:293)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at android.app.ActivityThread.loopProcess(ActivityThread.java:9824)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at android.app.ActivityThread.main(ActivityThread.java:9813)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at java.lang.reflect.Method.invoke(Native Method)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:586)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1201)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at com.huawei.hiai.utils.s.p(DeviceUtil.java:5)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at com.huawei.hiai.hiaid.hiaic.b.a(AbsSettingsManager.java:5)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at com.huawei.hiai.hiaid.hiaic.a.a(AIEngineSettingsManager.java:6)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at com.huawei.hiai.hiaid.hiaic.a.d(AIEngineSettingsManager.java:3)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at com.huawei.hiai.plugin.pushupdate.ResPackagePushUpdateJobService.a(ResPackagePushUpdateJobService.java:5)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at com.huawei.hiai.plugin.pushupdate.ResPackagePushUpdateJobService.onStartJob(ResPackagePushUpdateJobService.java:3)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at android.app.job.JobService$1.onStartJob(JobService.java:66)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : at android.app.job.JobServiceEngine$JobHandler.handleMessage(JobServiceEngine.java:121)  
05-14 17:07:23.182 18417-18417/? E AndroidRuntime/ : ... 8 more  

05-14 17:07:41.624 18542-18601/? F libc/ : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 18601 (RenderThread), pid 18542 (ample.animation)  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : Build fingerprint: 'HUAWEI/JAD-AN00/HWFCO:12/HUAWEIJAD-AN00/3.1.0.155SP50C00:userdebug/dev-keys'  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : Revision: '0'  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : ABI: 'x86_64'  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : Timestamp: 2024-05-14 17:07:41.997428200+0800  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : Process uptime: 27s  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : Cmdline: com.example.animation  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : pid: 18542, tid: 18601, name: RenderThread &gt;&gt;&gt; com.example.animation &lt;&lt;&lt;  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : uid: 10060  
05-14 17:07:42.980 18969-18969/? F DEBUG/ : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------  

05-14 21:46:19.927 7658-7658/? I ohsh/ : type=1400 audit(0.0:45818): avc: denied { connectto } for path="/dev/socket/containerd" scontext=u:r:shell:s0 tcontext=u:r:ohco_containerd:s0 tclass=unix_stream_socket permissive=1  
05-14 21:46:19.940 680-680/? E selinux_dmd/ : type=1400 audit(0.0:45818): avc: denied { connectto } for comm="ohsh" path="/dev/socket/containerd" scontext=u:r:shell:s0 tcontext=u:r:ohco_containerd:s0 tclass=unix_stream_socket permissive=1 find pid= failed  
05-14 21:46:19.941 680-680/? E selinux_dmd/ : type=1400 audit(0.0:45818): avc: denied { connectto } for comm="ohsh" path="/dev/socket/containerd" scontext=u:r:shell:s0 tcontext=u:r:ohco_containerd:s0 tclass=unix_stream_socket permissive=1 ExtractKeys failed  
05-14 21:46:19.949 7660-15000/? E libc/ : hidumper: Unable to open shared library libmemleak_tracker.so: dlopen failed: library "libmemleak_tracker.so" not found  
05-14 21:46:19.961 7660-15000/? D HiTraceC/ : entered HiTraceInit, Log Registered: 1  
05-14 21:46:20.003 7659-7659/? I containerd/ : [OHSH] fflush enter.  
05-14 21:46:20.004 7659-7659/? I containerd/ : destroy NameSpaceInfo 11.  
05-14 21:46:20.004 7659-7659/? I containerd/ : destroy NameSpaceInfo 10.  
05-14 21:46:20.004 7659-7659/? I containerd/ : destroy NameSpaceInfo 9.  
05-14 21:46:20.384 14983-15197/? I HwAmbientLuxFilterAlgo/ : t=17380109,lx=[0.0/17378507, 0.0/17378507, 0.0/17379307, 0.0/17379307, 0.0/17379307, 0.0/17380109],mLx=0.0,mOffLux=0.0,s=5.0,ss=0.0,Avened=false,mPxs=false,mTPxs=false,mBLux=2.0,mDlux=-1.0,mDt=5000,mBt=1300  
05-14 21:46:21.189 14983-14999/? I EventHub/ : EventHub monitor: no key events in the past 7287s, no motion events in the past 4674s  
05-14 21:46:21.932 14983-15005/? I EventHub/ : EventHub monitor: no key events in the past 7288s, no motion events in the past 4675s  
05-14 21:46:22.798 14983-15197/? I HwAmbientLuxFilterAlgo/ : t=17382511,lx=[0.0/17380910, 0.0/17380910, 0.0/17381712, 0.0/17381712, 0.0/17381712, 0.0/17382511],mLx=0.0,mOffLux=0.0,s=5.0,ss=0.0,Avened=false,mPxs=false,mTPxs=false,mBLux=2.0,mDlux=-1.0,mDt=5000,mBt=1300  
05-14 21:46:22.971 17840-17840/? I containerd/ : new connection  
05-14 21:46:22.972 17840-17840/? I containerd/ : Containerd MakeCmd. argv[0]: ohsh!  
05-14 21:46:22.972 17840-17840/? I containerd/ : Containerd MakeCmd. argv[1]: toybox!  
05-14 21:46:22.972 17840-17840/? I containerd/ : Containerd MakeCmd. argv[2]: ps!  
05-14 21:46:22.972 17840-17840/? I containerd/ : Containerd MakeCmd. argv[3]: -ef!  
05-14 21:46:22.972 17840-17840/? I containerd/ : [OHSH]do shell in  
05-14 21:46:22.972 17840-17840/? E containerd/ : [OHSH]stdout dup2  
05-14 21:46:22.972 17840-17840/? E containerd/ : [OHSH]stdout dup2  
05-14 21:46:22.974 17840-17840/? E containerd/ : eof  
05-14 21:46:22.974 17840-17840/? E containerd/ : failed to read size  
05-14 21:46:22.974 17840-17840/? I containerd/ : closing connection  
05-14 21:46:22.974 7668-7668/? I containerd/ : EnterNss NameSpaceInfo.  
05-14 21:46:22.975 7669-15004/? I containerd/ : [OHSH]RunCommand begin  
05-14 21:46:22.976 7669-15004/? I containerd/ : [ohsh]GetZygotePid PID 5!  
05-14 21:46:22.979 7669-15004/? E libc/ : toybox: Unable to open shared library libmemleak_tracker.so: dlopen failed: library "libmemleak_tracker.so" not found  
05-14 21:46:22.985 7668-7668/? I containerd/ : [OHSH] fflush enter.  
05-14 21:46:22.985 7668-7668/? I containerd/ : destroy NameSpaceInfo 11.  
05-14 21:46:22.985 7668-7668/? I containerd/ : destroy NameSpaceInfo 10.  
05-14 21:46:22.985 7668-7668/? I containerd/ : destroy NameSpaceInfo 9.  
05-14 21:46:24.220 707-707/? E thermal/-daemon: logPower_print not support

更多关于HarmonyOS 鸿蒙Next 使用本地模拟器跑官方示例,Log日志不断输出错误的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html

vueper 1楼•5 天前

设备运行时本身有很多日志信息，不是都需要关注，日志窗口上方对日志做个过滤，关注应用相关日志即可。模拟器本身用的是简化版系统，有些报错日志也属正常，运行应用主要关注是否应用本身导致错误。

更多关于HarmonyOS 鸿蒙Next 使用本地模拟器跑官方示例,Log日志不断输出错误的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html

sinazl 2楼•5 天前

在HarmonyOS鸿蒙Next中使用本地模拟器运行官方示例时，如果Log日志不断输出错误，可能是由于以下原因：

模拟器配置问题：模拟器的配置可能不符合示例的运行要求，导致资源分配不足或兼容性问题。
示例代码问题：官方示例代码可能存在Bug或未适配当前版本的鸿蒙Next，导致运行时出现错误。
依赖库问题：示例可能依赖某些库或服务，而这些库或服务在模拟器环境中未正确安装或配置。
系统资源限制：模拟器可能受到系统资源的限制，如内存、CPU等，导致无法正常运行示例。
日志级别设置：日志级别可能设置为调试或更详细级别，导致大量错误信息输出。
网络问题：如果示例需要网络连接，模拟器的网络配置可能存在问题，导致连接失败或超时。
权限问题：示例可能缺少必要的权限，导致无法访问某些资源或服务。
模拟器版本问题：模拟器版本可能与鸿蒙Next版本不兼容，导致运行时出现错误。
环境变量问题：环境变量可能未正确设置，导致示例无法找到必要的资源或配置。
日志输出配置：日志输出配置可能存在问题，导致错误信息被重复输出。

建议检查上述可能的原因，并根据具体错误信息进行排查和修复。

bupafengyu 3楼•5 天前

在HarmonyOS鸿蒙Next中使用本地模拟器运行官方示例时，若Log日志不断输出错误，可能原因包括：

模拟器配置不当，如内存不足或版本不匹配；
示例代码存在兼容性问题；
开发环境未正确设置。

建议检查模拟器配置，确保其与示例要求一致，并更新开发工具至最新版本。同时，查阅官方文档和社区论坛，寻找类似问题的解决方案。