skills.rest
hw-native-sys
hw-native-sysOFFICIAL
Explore all skills by this author →
GitHub

ascendc-runtime-debug

Diagnose Ascend C operator runtime errors via ACLNN error codes and plog analysis.

11|51|Updated Mar 10, 2026
Search Tags:#tiling#error-codes#runtime-debugging#ascend-c#plog-analysis#kernel-lookup
One-click install
npx skills add https://github.com/hw-native-sys/pypto-lib --skill ascendc-runtime-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ascendc-runtime-debug
Source: https://github.com/hw-native-sys/pypto-lib/tree/main/.claude/skills/cannbot-skills/ascendc-runtime-debug
Command: npx skills add https://github.com/hw-native-sys/pypto-lib --skill ascendc-runtime-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Ascend C operator runtime debugging systemizes troubleshooting for runtime errors including ACLNN error codes (161xxx/361xxx/561xxx), runtime exceptions (hangs, timeouts, core dumps), and plog-based investigations.

Core Features & Use Cases

  • Systematic error triage across tiling, kernel lookup, and runtime error categories
  • plog-driven debugging workflow with environment checks and repro steps
  • Practical use cases: diagnose stalls, kernel not found, or tiling failures in Ascend C operators.

Quick Start

Analyze the plog, error codes, and tiling status to identify and address the root runtime issue.

Frequently Asked Questions about ascendc-runtime-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug Ascend C operator runtime errors like 161xxx or 361xxx?▼

To debug Ascend C operator runtime errors, analyze ACLNN error codes and plog data to reproduce, isolate, and remediate issues. This systematic approach triages tiling failures, kernel lookup problems, and hangs across specific error code families.

What is the best way to analyze plog for Ascend C kernel lookup problems?▼

The best way to analyze plog for kernel lookup problems is applying a structured debugging workflow with environment checks. This isolates runtime exceptions and identifies root causes for stalls or kernel not found errors.

Why does my Ascend C operator fail during tiling?▼

Ascend C operator tiling failures occur due to runtime exceptions within the execution environment. Systematic error triage categorizes these failures alongside kernel lookup issues to isolate the root cause.

Can I diagnose Ascend C runtime hangs and core dumps using error codes?▼

Yes, you can diagnose Ascend C runtime hangs and core dumps using ACLNN error codes. Structured guidance maps error codes like 561xxx to specific runtime exceptions for targeted remediation.

What should I do when Ascend C runtime debugging does not resolve my memory issue?▼

When Ascend C runtime debugging does not resolve memory issues, verify your environment checks and plog reproduction steps. Limitations in tiling configurations or kernel lookup paths often require deeper isolation.

Related Skills

Explore More Software Engineering Skills→
hw-native-syshw-native-sys
11

ascendc-st-design

Design Ascend C operator tests via YAML-driven test plan and test-case generation.

Official
Advanced
AscendAscend
31

triton-operator-design

Generate Triton operator design documents for Ascend NPU.

Official
Advanced
hw-native-syshw-native-sys
11

ascendc-tiling-design

Design Ascend C tiling strategies with multi-core and UB buffer planning templates.

Official
Advanced
VanhPokerVanhPoker

nodejs-expert

Diagnose Node.js runtime issues in async patterns, module resolution, and performance.

Community
Advanced