Valgrind在android 5 / L崩溃

时间：2014-10-29 11:52:36

标签： android linux crash valgrind

我用NDK R10b交叉编译了Valgrind for android target eabi x86。 每个步骤启动我的应用程序时，例如here valgrind崩溃。 登录

10-29 11:16:07.468: D/AndroidRuntime(2240): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
10-29 11:16:07.469: D/AndroidRuntime(2240): CheckJNI is ON
10-29 11:16:07.486: E/memtrack(2240): Couldn't load memtrack module (No such file or directory)
10-29 11:16:07.486: E/android.os.Debug(2240): failed to load memtrack module: -2
10-29 11:16:07.500: D/AndroidRuntime(2240): Calling main entry com.android.commands.am.Am
10-29 11:16:07.502: I/ActivityManager(1236): START u0 {act=android.intent.action.MAIN flg=0x10000000 cmp=...} from uid 0 on display 0
10-29 11:16:07.518: D/AndroidRuntime(2240): Shutting down VM
10-29 11:16:07.519: I/art(2240): Debugger is no longer active
10-29 11:16:07.522: E/libprocessgroup(2250): failed to make and chown /acct/uid_10053: Read-only file system
10-29 11:16:07.522: W/Zygote(2250): createProcessGroup failed, kernel missing CONFIG_CGROUP_CPUACCT?
10-29 11:16:07.523: I/art(2250): Not late-enabling -Xcheck:jni (already on)
10-29 11:16:07.524: E/art(2240): Thread attaching while runtime is shutting down: Binder_1
10-29 11:16:07.524: I/AndroidRuntime(2240): NOTE: attach of thread 'Binder_1' failed
10-29 11:16:09.746: D/AndroidRuntime(2264): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
10-29 11:16:09.848: D/AndroidRuntime(2264): CheckJNI is ON
10-29 11:16:10.278: I/art(2264): Counter: 1
10-29 11:16:10.318: I/start-valgrind.sh(2263): No [stack] line found in /proc/self/maps!
10-29 11:16:10.321: A/libc(2264): No [stack] line found in /proc/self/maps!
10-29 11:16:10.341: A/libc(2264): Fatal signal 6 (SIGABRT), code -6 in tid 2264 (...)
10-29 11:16:10.580: I/DEBUG(948): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-29 11:16:10.580: I/DEBUG(948): Build fingerprint: 'generic_x86/sdk_phone_x86/generic_x86:5.0/LRX09D/1504858:eng/test-keys'
10-29 11:16:10.580: I/DEBUG(948): Revision: '0'
10-29 11:16:10.580: I/DEBUG(948): ABI: 'x86'
10-29 11:16:10.580: I/DEBUG(948): pid: 2264, tid: 2264, name: ...  >>> /data/local/Inst/bin/valgrind <<<
10-29 11:16:10.580: I/DEBUG(948): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
10-29 11:16:10.581: I/DEBUG(948): Abort message: 'No [stack] line found in /proc/self/maps!'
10-29 11:16:10.581: I/DEBUG(948):     eax 00000000  ebx 000008d8  ecx 00000006  edx 00000000
10-29 11:16:10.581: I/DEBUG(948):     esi 00000000  edi 00000000
10-29 11:16:10.581: I/DEBUG(948):     xcs 00000073  xds 0000007b  xes 0000007b  xfs 00000000  xss 0000007b
10-29 11:16:10.581: I/DEBUG(948):     eip 3806dd52  ebp 00000000  esp 628cfe40  flags 00200202
10-29 11:16:10.581: I/DEBUG(948): backtrace:
10-29 11:16:10.581: I/DEBUG(948):     #00 pc 0006dd52  /data/local/Inst/lib/valgrind/memcheck-x86-linux
10-29 11:16:10.583: W/NativeCrashListener(1236): Couldn't find ProcessRecord for pid 2264
10-29 11:16:10.597: I/DEBUG(948): Tombstone written to: /data/tombstones/tombstone_09
10-29 11:16:10.597: I/BootReceiver(1236): Copying /data/tombstones/tombstone_09 to DropBox (SYSTEM_TOMBSTONE)
10-29 11:16:10.637: I/start-valgrind.sh(2263): start-valgrind.sh terminated by exit(1)
10-29 11:16:10.638: I/Zygote(954): Process 2250 exited cleanly (1)
10-29 11:16:10.639: W/Zygote(954): Error reading pid from wrapped process, child may have died
10-29 11:16:10.639: W/Zygote(954): java.io.EOFException
10-29 11:16:10.639: W/Zygote(954): 	at libcore.io.Streams.readFully(Streams.java:83)
10-29 11:16:10.639: W/Zygote(954): 	at java.io.DataInputStream.readInt(DataInputStream.java:103)
10-29 11:16:10.639: W/Zygote(954): 	at com.android.internal.os.ZygoteConnection.handleParentProc(ZygoteConnection.java:974)
10-29 11:16:10.639: W/Zygote(954): 	at com.android.internal.os.ZygoteConnection.runOnce(ZygoteConnection.java:276)
10-29 11:16:10.639: W/Zygote(954): 	at com.android.internal.os.ZygoteInit.runSelectLoop(ZygoteInit.java:784)
10-29 11:16:10.639: W/Zygote(954): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:690)
10-29 11:16:10.639: W/ActivityManager(1236): Slow operation: 3129ms so far, now at startProcess: returned from zygote!
10-29 11:16:10.639: W/ActivityManager(1236): Slow operation: 3129ms so far, now at startProcess: done updating battery stats
10-29 11:16:10.639: W/ActivityManager(1236): Slow operation: 3129ms so far, now at startProcess: building log message
10-29 11:16:10.639: I/ActivityManager(1236): Start proc ... for activity ...: pid=2250 uid=10053 gids={50053, 9997, 3003, 1028, 1015} abi=x86
10-29 11:16:10.640: W/ActivityManager(1236): Slow operation: 3129ms so far, now at startProcess: starting to update pids map
10-29 11:16:10.640: W/ActivityManager(1236): Slow operation: 3130ms so far, now at startProcess: done updating pids map
10-29 11:16:10.640: W/ActivityManager(1236): Slow operation: 3130ms so far, now at startProcess: done starting proc!
10-29 11:16:17.520: W/ActivityManager(1236): Launch timeout has expired, giving up wake lock!
10-29 11:16:20.650: W/ActivityManager(1236): Process ProcessRecord{1daddf3b 2250:.../u0a53} failed to attach
10-29 11:16:20.650: I/ActivityManager(1236): Killing 2250:.../u0a53 (adj -100): start timeout

  1. 这也适用于Android 5 / L的ARM模拟器
  2. 我正在使用ubuntu 14
  3. 手动valgrind启动，例如/ data / local / Inst / bin / valgrind / data / local / sample-bin工作没有问题
  4. 这在模拟器API 18（ARM）上使用相同的Valgrind编译工作正常
  5. 我尝试使用在允许写入模式下重新安装文件系统 adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system 和 mount -o ro,remount /system 和 adb root && adb remount - 没有诀窍

    6. 有没有人有任何想法可能会出现问题？

2 个答案:

答案 0 :(得分：3)

我在模拟器的Widget预览应用程序中遇到了类似的错误：

E/libprocessgroup﹕ failed to make and chown /acct/uid_10052: Read-only file system

经过各种网络搜索和实验，我发现模拟器的/sdcard确实设置为只读。 （您可以通过尝试触摸或推送adb shell中的文件，或使用Android设备管理器来浏览文件系统来测试此。）

Issue 78434中描述了有效的错误和解决方法。

解决方法

  • 转到.android文件夹中的ADV文件夹，找到您的AVD的config.ini文件，例如~/.android/avd/Nexus5_v19.avd/config.ini。
  • 使用文本编辑器打开它。如果您使用的是Windows，请使用可以处理Unix换行符的文本编辑器。
  • 将hw.sdCard=no更改为hw.sdCard=yes。
  • 保存，重新启动模拟器，并测试/ sdcard是否可写。

答案 1 :(得分：0)

好的，我遇到了同样的问题，而上述解决方案对我来说并不起作用。在我将Firebase存储添加到我的应用程序之后，我发现了它。 检查build.gradle(Module:app)，发现Firebase的不同版本冲突，将所有版本更改为同一版本，同步项目，现在可以正常运行:)希望此帮助以供将来参考。

相关问题
最新问题