Interrupting Execution
- When the operator execution program on the host or device suspends, enter CTRL+C to manually interrupt the operator execution program and display the interrupted location.
If the program suspends, enter CTRL+C to stop the program. The possible causes are as follows:- The user program itself has an infinite loop, which needs to be rectified by repairing the program.
- An operator uses synchronization instructions.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
(msdebug) r Process 173221 launched: '${INSTALL_DIR}/projects/mix/matmul_leakyrelu.fatbin' (aarch64) [Launch of Kernel matmul_leakyrelu_custom on Device 1] // Enter CTRL+C. Process 173221 stopped [Switching to focus on Kernel matmul_leakyrelu_custom, CoreId 35, Type aiv] * thread #1, name = 'matmul_leakyrel', stop reason = signal SIGSTOP frame #0: 0x000000000000ef5c device_debugdata`_ZN17MatmulLeakyKernelIDhDhffE10CalcOffsetEiiRK11TCubeTilingRiS4_S4_S4__mix_aiv(this=<unavailable>, blockIdx=<unavailable>, usedCoreNum=<unavailable>, tiling=<unavailable>, offsetA=<unavailable>, offsetB=<unavailable>, offsetC=<unavailable>, offsetBias=<unavailable>) at matmul_leakyrelu_kernel.cpp:127:5 124 auto mCoreIndx = blockIdx % mSingleBlocks; 125 auto nCoreIndx = blockIdx / mSingleBlocks; 126 -> 127 while(true) { 128 } 129 offsetA = mCoreIndx * tiling.Ka * tiling.singleCoreM; 130 offsetB = nCoreIndx * tiling.singleCoreN; (msdebug)
- After the debugging is complete, run the q command and enter Y or y to end the debugging.
(msdebug) q Quitting LLDB will kill one or more processes. Do you really want to proceed: [Y/n] y
- This function can debug only the operator programs started in msDebug.
- After the interruption takes effect, only Displaying the Debugging Information and Switching Cores functions are supported, and Executing Step-by-Step Debugging, Reading Register Values, Printing Memory and Variables, and continue commands are not supported.
Parent topic: msDebug (Operator Debugging)