slog-debugging

Analyze Agoric slog files and flight recorder data to diagnose vat delivery failures.

3|2|Updated May 12, 2026

Search Tags:#debugging #slog #flight-recorder #agoric #swingset #xsnap

Ready to run

npx skills add https://github.com/kriscendobot/garden --skill slog-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slog-debugging
Source: https://github.com/kriscendobot/garden/tree/main/skills/slog-debugging
Command: npx skills add https://github.com/kriscendobot/garden --skill slog-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the difficulty of diagnosing complex failures in Agoric swingset environments by providing a structured method to interpret slog files and flight recorder binary data.

Core Features & Use Cases

Artifact Preservation: Provides clear instructions on how to capture and save the flight recorder binary before test teardown prevents data loss.
Failure Classification: Enables precise identification of XS engine errors, such as stack meter exhaustion, by correlating slog records with delivery outcomes.
Root Cause Analysis: Guides the user through walking back from error records to the specific vat delivery and incarnation that triggered the failure.

Quick Start

Use the slog-debugging skill to identify the failing delivery in the captured flight-recorder.bin file.

Frequently Asked Questions about slog-debugging

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

FAQPage Schema

How do I debug Agoric swingset vat delivery failures?▼

To debug Agoric swingset vat delivery failures, you analyze slog files and flight recorder binary data to correlate kernel-level events with specific XS engine aborts. This process isolates the root cause by tracking the failing vat delivery and its incarnation.

What is a flight recorder binary in Agoric XS engine debugging?▼

A flight recorder binary in Agoric XS engine debugging is captured runtime data that preserves the state before a crash. It is required to trace back from stack meter exhaustion errors to the specific vat delivery that triggered the failure.

How do I capture flight recorder data before test teardown prevents data loss?▼

To capture flight recorder data before test teardown, you must explicitly save the flight-recorder.bin file immediately upon detecting an XS engine abort. Preserving this artifact prevents data loss and allows subsequent grep-based log parsing.

How do I find the root cause of an XS engine stack meter exhaustion abort?▼

To find the root cause of an XS engine stack meter exhaustion abort, you walk back from the error records in the slog to the specific vat delivery. You use incarnation tracking to isolate the exact delivery that triggered the failure.

Does slog debugging require grep for parsing Agoric swingset logs?▼

Yes, slog debugging requires systematic grep-based log parsing to filter Agoric swingset records. Grep is utilized to extract relevant kernel-level events from the slog file and correlate them with delivery outcomes.

Can I diagnose xsnap aborts using slog files in agoric-sdk development?▼

Yes, you can diagnose xsnap aborts using slog files in agoric-sdk development. By correlating slog records with flight recorder data, you systematically identify the specific XS engine errors and isolate the failing vat incarnation.