strace-ltrace

Trace Linux binary system and library calls to diagnose errors without crashing.

Updated Aug 27, 2026

Search Tags:#debugging #trace #diagnostics #syscalls #strace #ltrace #library-calls

Ready to run

npx skills add https://github.com/awfixers-stuff/opencode-config --skill strace-ltrace-awfixers-stuff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: strace-ltrace
Source: https://github.com/awfixers-stuff/opencode-config/tree/main/skills/strace-ltrace
Command: npx skills add https://github.com/awfixers-stuff/opencode-config --skill strace-ltrace-awfixers-stuff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Trace system calls and library calls to diagnose binary behavior without crashing or requiring a debugger.

Core Features & Use Cases

Trace kernel interactions with strace to observe system calls (e.g., open, read, connect) and capture failures.
Trace user-space library calls with ltrace to understand library function usage and failures.
Use cases include debugging ENOENT/EPERM errors, permission issues, file and network activity, and dynamic library loading problems without altering the program.

Quick Start

Start tracing by running strace on the target binary to observe system calls and attach ltrace to monitor library calls.

Frequently Asked Questions about strace-ltrace

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

FAQPage Schema

How do I trace system calls to diagnose why a Linux binary fails with ENOENT or EPERM?▼

Trace system calls with strace to observe kernel interactions like open, read, and connect, capturing specific failures such as ENOENT or EPERM without altering or crashing the program. This reveals exact permission errors and file activity.

What is the best way to debug dynamic library loading issues without attaching a debugger?▼

Debug dynamic library loading issues by tracing user-space library calls with ltrace to understand library function usage and failures. This allows you to observe dynamic library behavior without crashing the binary or requiring a full debugger.

Can I trace file and network activity for a running Linux process without stopping it?▼

Yes, you can trace file and network activity for a running process by attaching strace and ltrace to the existing process. This captures system calls and library calls on the fly to diagnose binary behavior without crashing the program.

How do I interpret strace output to find permission errors and failed syscalls?▼

Interpret strace output by using guided workflows that highlight common error patterns. This helps you quickly identify failed syscalls, permission errors, and network activity within the trace logs to pinpoint the exact failure point.

When should I use ltrace instead of strace to diagnose binary behavior?▼

Use ltrace instead of strace when you need to understand user-space library function usage and failures, whereas strace is better for observing kernel-level syscalls. Both diagnose binary behavior without crashing, focusing on different interaction layers.