runtime-errors

Diagnose runtime query errors using Sirius logs and debugging tools.

1.0k|109|Updated Jun 19, 2024
One-click install
npx skills add https://github.com/sirius-db/sirius --skill runtime-errors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-errors
Source: https://github.com/sirius-db/sirius/tree/main/.claude/skills/runtime-errors
Command: npx skills add https://github.com/sirius-db/sirius --skill runtime-errors

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and fix issues when your queries crash, hang, throw exceptions, or unexpectedly fall back to CPU execution.

Core Features & Use Cases

  • Error Triage: Classifies errors into Hang, Segfault, or Runtime categories for targeted debugging.
  • Log Analysis: Examines detailed logs to pinpoint the source of failures.
  • Debugging Tools: Integrates with cuda-gdb, Compute Sanitizer, and AddressSanitizer for deep system-level analysis.
  • Use Case: If a complex SQL query analyzing large datasets suddenly crashes with a segmentation fault, this Skill can analyze the backtrace and logs to identify the exact line of code causing the issue and suggest a fix.

Quick Start

Use the runtime-errors skill to diagnose a query that is crashing with a segmentation fault.

Frequently Asked Questions about runtime-errors

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

FAQPage Schema
How do I debug a segmentation fault or crash during query execution?

To debug a segmentation fault during query execution, analyze Sirius log files and backtraces to pinpoint the source code line. This Skill classifies the crash and suggests a targeted fix to resolve the failure.

What is the best way to diagnose SQL queries that hang or unexpectedly fall back to CPU execution?

Diagnose SQL query hangs or unexpected CPU fallbacks by examining Sirius logs and reproducing the query with specific timeout parameters. This classifies the behavior to identify the execution bottleneck causing the issue.

Can I use cuda-gdb and Compute Sanitizer to analyze runtime errors in my queries?

Yes, you can use cuda-gdb and Compute Sanitizer to analyze query runtime errors. This Skill integrates these tools alongside AddressSanitizer to perform deep system-level analysis on crashes and segmentation faults.

How do I find the exact line of code causing a runtime exception in a large dataset query?

To find the exact code line causing a runtime exception in a large dataset query, examine detailed Sirius logs and backtraces. Error triage classifies the exception to target the precise failure source.

What do I need to reproduce and resolve unexpected query crashes?

To reproduce and resolve unexpected query crashes, you need specific query inputs and optional timeout parameters. This allows the debugging process to replicate the runtime error and analyze logs for the root cause.