skills.rest
JYbill
JYbillCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

nodejs-core

Debug C++ bindings and V8 internals to resolve Node.js native addon crashes.

1|Updated Mar 14, 2025
Search Tags:#debugging#nodejs#gdb#lldb#inspector#v8#native-addons
One-click install
npx skills add https://github.com/JYbill/bullboard-nestjs --skill nodejs-core-jybill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nodejs-core
Source: https://github.com/JYbill/bullboard-nestjs/tree/main/.claude/skills/nodejs-core
Command: npx skills add https://github.com/JYbill/bullboard-nestjs --skill nodejs-core-jybill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging crashes and performance issues in Node.js native addons by inspecting C++ bindings, V8 internals, and libuv event loop.

Core Features & Use Cases

  • Diagnose segfaults, memory leaks, and hangs in native modules and bindings.
  • Guide for using gdb/lldb, Valgrind/ASan, V8 profiling, and N-API debugging patterns.
  • Apply across Windows/macOS/Linux builds, including node-gyp/binding.gyp workflows.

Quick Start

Start a debugging session with gdb or lldb against your Node.js process, then load V8 internals and inspect native stack frames to identify root causes.

Frequently Asked Questions about nodejs-core

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

FAQPage Schema
How do I debug a segmentation fault in Node.js native addons?▼

Debug segmentation faults in Node.js native addons by attaching gdb or lldb to the process, loading V8 internals, and inspecting native C++ stack frames to identify the root cause.

What is the best way to trace memory leaks in Node.js native modules?▼

Trace memory leaks in Node.js native modules by using Valgrind or AddressSanitizer (ASan) alongside V8 profiling tools to detect memory allocation issues within your C++ bindings.

How do I resolve libuv event loop stalls caused by native code?▼

Resolve libuv event loop stalls by profiling your Node.js process to identify blocking operations in native code, then applying V8 tracing to inspect the stalled event loop frames.

Can I use gdb and lldb to debug Node.js native addons across different operating systems?▼

Yes, you can debug Node.js native addons across Windows, macOS, and Linux by using gdb for Linux and lldb for macOS, allowing you to inspect C++ bindings consistently across platforms.

How do I fix node-gyp build-time issues for Node.js native addons?▼

Fix node-gyp build-time issues by examining your binding.gyp workflows and ensuring your C++ bindings correctly compile across Windows, macOS, and Linux environments before runtime debugging.

When should I use N-API debugging patterns for Node.js native addons?▼

Use N-API debugging patterns when diagnosing crashes and performance issues in Node.js native addons, as these patterns help inspect C++ bindings and V8 internals more effectively during native module troubleshooting.

Related Skills

Explore More Software Engineering Skills→
hckhanhhckhanh
3

ctx-upgrade

Fetch, build, install, and configure the Context Mode plugin automatically.

Community
Intermediate
novvoonovvoo

nodejs-core

Debug Node.js native addons with GDB/LLDB and analyze core dumps.

Community
Advanced
theodo-grouptheodo-group
157

dbg

Debug Node.js, Bun, and native programs via CDP, JSC, and LLDB/DAP.

Official
Intermediate
linfordWulinfordWu
1

vmcore-analysis

Analyze Linux kernel VMcore crash dumps and generate root-cause reports.

Community
Advanced