Scribd Logo
Upload

Welcome to Scribd!

  • Limbo Log

    Uploaded by

    fattah faih
    22 views3 pages
    The document contains log entries from an Android application crash. It shows that the application crashed with a NullPointerException when trying to delete an observer from a machine object that was null. The logs also show the application starting a QEMU virtual machine emulator with parameters like the CPU, memory size, and virtual disk files.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document contains log entries from an Android application crash. It shows that the application crashed with a NullPointerException when trying to delete an observer from a machine object that was null. The logs also show the application starting a QEMU virtual machine emulator with parameters like the CPU, memory size, and virtual disk files.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    22 views3 pages

    Limbo Log

    Uploaded by

    fattah faih
    The document contains log entries from an Android application crash. It shows that the application crashed with a NullPointerException when trying to delete an observer from a machine object that was null. The logs also show the application starting a QEMU virtual machine emulator with parameters like the CPU, memory size, and virtual disk files.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    of 3

    --------- beginning of crash

    02-14 16:08:55.346 10499 13218 F libc : FORTIFY: pthread_mutex_lock called on a


    destroyed mutex (0x7d3ea7d298)
    02-14 16:08:55.346 10499 13218 F libc : Fatal signal 6 (SIGABRT), code -1
    (SI_QUEUE) in tid 13218 (LimboLogger), pid 10499 (bo.emu.main.arm)
    02-14 16:08:55.404 10499 13216 F libc : FORTIFY: pthread_mutex_lock called on a
    destroyed mutex (0x7dca3f8aa0)
    02-14 16:08:55.404 10499 13215 F libc : FORTIFY: pthread_mutex_lock called on a
    destroyed mutex (0x7dca3f8aa0)
    02-14 16:08:55.422 13234 13234 F DEBUG : *** *** *** *** *** *** *** *** *** ***
    *** *** *** *** *** ***
    02-14 16:08:55.423 13234 13234 F DEBUG : Build fingerprint:
    'Redmi/begonia/begonia:11/RP1A.200720.011/V12.5.8.0.RGGMIXM:user/release-keys'
    02-14 16:08:55.423 13234 13234 F DEBUG : Revision: '0'
    02-14 16:08:55.423 13234 13234 F DEBUG : ABI: 'arm64'
    02-14 16:08:55.423 13234 13234 F DEBUG : Timestamp: 2023-02-14 16:08:55+0100
    02-14 16:08:55.423 13234 13234 F DEBUG : pid: 10499, tid: 13218, name:
    LimboLogger >>> com.limbo.emu.main.arm <<<
    02-14 16:08:55.423 13234 13234 F DEBUG : uid: 10253
    02-14 16:08:55.423 13234 13234 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE),
    fault addr --------
    02-14 16:08:55.423 13234 13234 F DEBUG : Abort message: 'FORTIFY:
    pthread_mutex_lock called on a destroyed mutex (0x7d3ea7d298)'
    02-14 16:08:55.423 13234 13234 F DEBUG : x0 0000000000000000 x1
    00000000000033a2 x2 0000000000000006 x3 0000007cce8f0a20
    02-14 16:08:55.423 13234 13234 F DEBUG : x4 0000000000008080 x5
    0000000000008080 x6 0000000000008080 x7 0000000000000038
    02-14 16:08:55.423 13234 13234 F DEBUG : x8 00000000000000f0 x9
    0000007dcb780718 x10 ffffff80fffffbdf x11 0000000000000001
    02-14 16:08:55.423 13234 13234 F DEBUG : x12 0000000000000030 x13
    0000000063eba407 x14 001491766368cd85 x15 000010c75f627a73
    02-14 16:08:55.423 13234 13234 F DEBUG : x16 0000007dcb852948 x17
    0000007dcb830f80 x18 0000007c9940c000 x19 00000000000000ac
    02-14 16:08:55.423 13234 13234 F DEBUG : x20 0000000000002903 x21
    00000000000000b2 x22 00000000000033a2 x23 00000000ffffffff
    02-14 16:08:55.423 13234 13234 F DEBUG : x24 0000007cce8f1fb8 x25
    0000007cce266620 x26 0000000000000000 x27 0000000000000002
    02-14 16:08:55.423 13234 13234 F DEBUG : x28 0000000000000000 x29
    0000007cce8f0aa0
    02-14 16:08:55.423 13234 13234 F DEBUG : lr 0000007dcb7e3fc4 sp
    0000007cce8f0a00 pc 0000007dcb7e3ff4 pst 0000000000001000
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: FATAL EXCEPTION: main
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: Process: com.limbo.emu.main.arm,
    PID: 13654
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: java.lang.RuntimeException: Unable
    to destroy activity
    {com.limbo.emu.main.arm/com.limbo.emu.main.arm.LimboEmuActivity}:
    java.lang.NullPointerException: Attempt to invoke virtual method 'void
    com.max2idea.android.limbo.machine.Machine.deleteObserver(java.util.Observer)' on a
    null object reference
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.ActivityThread.performDestroyActivity(ActivityThread.java:5291)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:5320)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.servertransaction.DestroyActivityItem.execute(DestroyActivityItem.java:
    44)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.servertransaction.TransactionExecutor.executeLifecycleState(Transaction
    Executor.java:176)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:
    97)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.ActivityThread$H.handleMessage(ActivityThread.java:2187)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.os.Handler.dispatchMessage(Handler.java:106)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.os.Looper.loop(Looper.java:236)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.ActivityThread.main(ActivityThread.java:8057)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    java.lang.reflect.Method.invoke(Native Method)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:620)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1011)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: Caused by:
    java.lang.NullPointerException: Attempt to invoke virtual method 'void
    com.max2idea.android.limbo.machine.Machine.deleteObserver(java.util.Observer)' on a
    null object reference
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    com.max2idea.android.limbo.main.LimboActivity.onDestroy(LimboActivity.java:2426)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.Activity.performDestroy(Activity.java:8428)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.Instrumentation.callActivityOnDestroy(Instrumentation.java:1344)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: at
    android.app.ActivityThread.performDestroyActivity(ActivityThread.java:5276)
    02-14 16:15:48.291 13654 13654 E AndroidRuntime: ... 11 more
    --------- beginning of main
    02-14 17:13:16.887 17348 17348 I InputTransport: Create ARC handle: 0x7d346e7400
    02-14 17:13:16.889 17348 17348 I Toast : Show toast from
    OpPackageName:com.limbo.emu.main.arm, PackageName:com.limbo.emu.main.arm
    02-14 17:13:17.219 17348 17470 W Choreographer: Frame time is 7.02271 ms in the
    future! Check that graphics HAL is generating vsync timestamps using the correct
    timebase.
    02-14 17:13:17.371 17348 17348 V PhoneWindow: DecorView setVisiblity: visibility =
    4, Parent = android.view.ViewRootImpl@68a2c1f, this =
    DecorView@1406b6c[LimboEmuActivity]
    02-14 17:13:17.881 17348 17472 D MachineService: Starting VM: windows
    02-14 17:13:17.886 17348 17348 E libc : Access denied finding property
    "ro.vendor.pref_scale_resolution"
    02-14 17:13:17.890 17348 17472 D VMExecutor: Params:
    02-14 17:13:17.890 17348 17472 D VMExecutor: 0: libqemu-system-aarch64.so
    02-14 17:13:17.890 17348 17472 D VMExecutor: 1: -monitor
    02-14 17:13:17.890 17348 17472 D VMExecutor: 2: none
    02-14 17:13:17.890 17348 17472 D VMExecutor: 3: -serial
    02-14 17:13:17.890 17348 17472 D VMExecutor: 4: none
    02-14 17:13:17.891 17348 17472 D VMExecutor: 5: -parallel
    02-14 17:13:17.891 17348 17472 D VMExecutor: 6: none
    02-14 17:13:17.891 17348 17472 D VMExecutor: 7: -k
    02-14 17:13:17.891 17348 17472 D VMExecutor: 8: en-us
    02-14 17:13:17.891 17348 17472 D VMExecutor: 9: -smp
    02-14 17:13:17.891 17348 17472 D VMExecutor: 10: 4
    02-14 17:13:17.891 17348 17472 D VMExecutor: 11: -M
    02-14 17:13:17.891 17348 17472 D VMExecutor: 12: collie
    02-14 17:13:17.891 17348 17472 D VMExecutor: 13: -m
    02-14 17:13:17.891 17348 17472 D VMExecutor: 14: 512
    02-14 17:13:17.891 17348 17472 D VMExecutor: 15: -drive
    02-14 17:13:17.891 17348 17472 D VMExecutor: 16:
    index=0,if=ide,media=disk,file=/storage/emulated/0/Download/New Folder 1/windows 7
    pro.img
    02-14 17:13:17.891 17348 17472 D VMExecutor: 17: -drive
    02-14 17:13:17.891 17348 17472 D VMExecutor: 18:
    index=2,if=ide,media=cdrom,file=/storage/emulated/0/Download/Windows10.qcow2
    02-14 17:13:17.891 17348 17472 D VMExecutor: 19: -vga
    02-14 17:13:17.891 17348 17472 D VMExecutor: 20: std
    02-14 17:13:17.891 17348 17472 D VMExecutor: 21: -net
    02-14 17:13:17.891 17348 17472 D VMExecutor: 22: user
    02-14 17:13:17.891 17348 17472 D VMExecutor: 23: -net
    02-14 17:13:17.891 17348 17472 D VMExecutor: 24: nic,model=rtl8139
    02-14 17:13:17.891 17348 17472 D VMExecutor: 25: -L
    02-14 17:13:17.891 17348 17472 D VMExecutor: 26:
    /data/user/0/com.limbo.emu.main.arm/cache/limbo/
    02-14 17:13:17.891 17348 17472 D VMExecutor: 27: -qmp
    02-14 17:13:17.891 17348 17472 D VMExecutor: 28:
    unix:/data/user/0/com.limbo.emu.main.arm/cache/qmpsocket,server,nowait
    02-14 17:13:17.891 17348 17472 D VMExecutor: 29: -overcommit
    02-14 17:13:17.891 17348 17472 D VMExecutor: 30: mem-lock=off
    02-14 17:13:17.891 17348 17472 D VMExecutor: 31: -rtc
    02-14 17:13:17.891 17348 17472 D VMExecutor: 32: base=localtime
    02-14 17:13:17.891 17348 17472 D VMExecutor: 33: -nodefaults
    02-14 17:13:17.891 17348 17472 D VMExecutor: 34: -accel
    02-14 17:13:17.891 17348 17472 D VMExecutor: 35: tcg,thread=multi
    02-14 17:13:17.892 17348 17472 V vm-executor-jni.c: Processing params
    02-14 17:13:17.892 17348 17472 D vm-executor-jni.c: Starting VM
    02-14 17:13:17.892 17348 17472 V vm-executor-jni.c: Loading lib:
    /data/app/~~8MYun2iXGMvWmgd_IONpkw==/com.limbo.emu.main.arm-
    hMTTW8OUdOGLWChSLRvSug==/lib/arm64/libqemu-system-aarch64.so
    02-14 17:13:17.893 17348 17472 D limbo_compat_filesystem.c: Closing fd: 113
    02-14 17:13:17.896 17348 17472 W limbo_compat_filesystem.c: Could not fopen:
    /data/user/0/com.limbo.emu.main.arm/cache/limbo//usr/local/etc/qemu/qemu.conf, r,
    0x0
    02-14 17:13:17.910 17348 17472 E limbo_logutils.h: libqemu-system-aarch64.so:
    02-14 17:13:17.910 17348 17472 E limbo_logutils.h:
    02-14 17:13:17.910 17348 17472 E limbo_logutils.h: Invalid SMP CPUs 4. The max CPUs
    supported by machine 'collie' is 1
    02-14 17:13:17.910 17348 17472 E limbo_logutils.h:
    02-14 17:13:17.912 17348 17472 D libFrameRecord: unloaded from
    com.limbo.emu.main.arm

    You might also like