Searched refs:crash (Results 1 – 25 of 29) sorted by relevance
12
14 # echo c > /proc/sysrq-trigger // force trigger a crash17 Then you will see following message showing that crash is detected and the21 [ 14.949892][ T148] sysrq: Trigger a crash22 [ 14.952133][ T148] Kernel panic - not syncing: sysrq triggered crash69 ### Building the crash(8) tool71 You first need to build the crash(8) tool for the target architecture, which in most case is aarch6…76 $ wget https://github.com/crash-utility/crash/archive/refs/tags/8.0.2.tar.gz -O - | tar xzv77 $ make -j -C crash-8.0.2 target=ARM64101 ### Running crash(8) with the RAM dump and the kernel image104 $ crash-8.0.2/crash ramdump vmlinux[all …]
118 * Capturing userspace crash dump (only for Microdroid)
9 2. [Reproducing crash case](#reproducing_crash_case)10 3. [Finding minimal crash case](#finding_minimal_crash_case)21 This document seeks to be a crash-course and cheat-sheet for running the NNAPI77 appropriately, as everything is built as one unit. Finally, whenever a crash135 * `crash-*` -- any future problematic test cases will be dumped to the directory152 When something unexpected occurs (e.g., a crash or a very slow test case), the155 `slow-unit-<unique_identifier>`, `crash-<unique_identifier>`,157 `libFuzzer` crash files will contain unreadable binary data; however,164 ## Reproducing crash case <a id="reproducing_crash_case"></a>166 When a crash occurs, the crash test case can be re-run with the following[all …]
112 fun doTestReturn(crash: Boolean) = tryTest { in testReturn()113 if (crash) throw RuntimeException() else resultIfSuccess in testReturn()119 assertEquals(resultIfSuccess, doTestReturn(crash = false)) in testReturn()120 assertEquals(resultIfException, doTestReturn(crash = true)) in testReturn()
109 var crash: InterpretException? = null in <lambda>() variable117 if (null != crash) return@Thread in <lambda>()127 crash = InterpretException(threadIndex, it, in <lambda>()137 crash?.let { throw it } in <lambda>()
176 * google-breakpad: host binary crash handler177 * libunwindstack: print stacktrace on crash on host200 * LOG_ALWAYS_FATAL(fmt, args...): Enabled, will always crash201 * ASSERT(condition): Enabled, will crash when condition is false202 * ASSERT_LOG(conditon, fmt, args...): Enabled, will crash and print log when205 In general, errors that are caused by remote device should never crash our stack209 LOG_ALWAYS_FATAL() to crash the stack and restart.
152 final String crash = checkCrash(context, label, startTime); in getSystemHealthMessage() local153 if (crash != null) errors.append(crash); in getSystemHealthMessage()
85 R.drawable.crash, in query()96 R.drawable.crash, in query()
14 adb shell am crash com.android.systemui
21 crash.
26 adb shell am crash com.android.systemui
36 Database missing migration path or test could result in loss of db data and in worst case a crash a…39 * A deleted/altered field could lead to a crash due to incompatible data
7 # stack traces on uncaught exceptions, which is necessary to get useful crash
65 reproduce a crash.
93 // Collects app crash events.
855 com.king.crash 102282980 air.com.pixelstudio8.venom.angry.crash.rush.io.online 102304070 com.racing.car.crash.turbo 102324444 com.real.bumper.car.crash 10244,102427209 com.play.io.monster.truck.demolition.derby.crash.stunts 10232
1dictionary=main:it,locale=it,description=Italiano,date=1414726258, ...
1dictionary=main:pt_br,locale=pt_BR,description=Português (Brasil),date ...
1dictionary=main:da,locale=da,description=Dansk,date=1393228134, ...