skills.rest
fasterthanlime
fasterthanlimeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cranelift-debugging

Debug Cranelift JIT code with CDB/WinDbg, LLDB/GDB, and disassembly analysis.

Updated Aug 23, 2026
Search Tags:#debugging#gdb#cranelift#jit#cdb#lldb
One-click install
npx skills add https://github.com/fasterthanlime/.claude --skill cranelift-debugging
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cranelift-debugging
Source: https://github.com/fasterthanlime/.claude/tree/main/skills/cranelift-debugging
Command: npx skills add https://github.com/fasterthanlime/.claude --skill cranelift-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Debug crashes and memory issues in Cranelift-generated JIT code, including Windows and Unix workflows.

Core Features & Use Cases

  • Windows debugging with CDB/WinDbg
  • Unix debugging with LLDB/GDB and SIGSEGV handlers
  • Disassembly analysis for Cranelift-generated code

Quick Start

Attach a debugger to the test binary and inspect registers, backtrace, and disassembly around the crash.

Frequently Asked Questions about cranelift-debugging

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

FAQPage Schema
How do I debug crashes in Cranelift JIT-compiled code?▼

Attach a debugger (GDB/LLDB on Unix, CDB/WinDbg on Windows) to your JIT process, set breakpoints in the generated code, and inspect registers and memory around the crash site. Use disassembly to correlate Cranelift-generated instructions with the failure.

Can I debug Cranelift JIT code on Windows with CDB or WinDbg?▼

Yes. CDB and WinDbg support debugging Cranelift JIT crashes on Windows. Handle x64 ABI quirks when inspecting registers and stack frames, and use disassembly workflows to analyze dynamically generated code.

What's the best way to investigate memory corruption in JIT-generated code?▼

Use a debugger's memory inspection tools and disassembly analysis to trace memory writes in Cranelift-generated instructions. On Unix, SIGSEGV handlers help pinpoint faults; verify calling conventions match your platform's ABI.

Do I need to handle calling conventions differently when debugging JIT code?▼

Yes. Cranelift JIT debugging requires understanding calling-convention differences between Windows (x64 ABI) and Unix (System V). Inspect register and stack state carefully to verify function prologues and argument passing match expected conventions.

How do I use LLDB or GDB to debug Cranelift JIT memory issues on Unix?▼

Attach LLDB or GDB to the JIT process, set breakpoints in generated code, and inspect registers and memory. Use disassembly to correlate crashes with Cranelift-generated instructions, and leverage SIGSEGV handlers to catch segmentation faults.

What debuggers work with Cranelift JIT code on different platforms?▼

GDB and LLDB debug Cranelift JIT on Unix; CDB and WinDbg debug on Windows. All support register inspection, disassembly analysis, and breakpoint workflows needed to diagnose crashes and memory corruption in dynamically generated code.

Related Skills

Explore More Software Engineering Skills→
Pama-LeePama-Lee

ordo-jit-optimization

...

Community
Advanced
openharmonyinsightopenharmonyinsight
31

ohos-issue-graphics-cppcrash-analysis

Analyze OpenHarmony cppcrash logs to locate native graphics crash root causes.

Official
Advanced
BlitterStudioBlitterStudio
947

amiberry-jit-fix

Fixes ARM64 JIT compiler crashes and visual corruption in the Amiberry emulator.

Official
Advanced
philo-grovesphilo-groves
12

maxtac-dast-debugger

Integrate debuggers, instrumentation, and crash replay for binary dynamic analysis.

Community
Advanced