Reference
Common Windows issues
Section titled “Common Windows issues”std::bad_alloc appearing as STATUS_STACK_BUFFER_OVERRUN
Section titled “std::bad_alloc appearing as STATUS_STACK_BUFFER_OVERRUN”Cause: Unhandled exception → terminate → abort → /GS check
Solutions:
- Prevent it: Use the Build Governor (
.\scripts\setup-governor.ps1) - Diagnose it: Use crash handlers to see the real exception
Missing symbols in stack traces
Section titled “Missing symbols in stack traces”Cause: No PDB files for release builds
Solution: Build with /Zi and /DEBUG linker flag
Build hangs or system freezes
Section titled “Build hangs or system freezes”Cause: Too many parallel compilations exhausting commit charge
Solution: The Build Governor automatically throttles based on memory pressure
Toolkit files
Section titled “Toolkit files”| File | Purpose |
|---|---|
src/crash_handlers.h | Verbose crash diagnostics |
src/debug_log.h | Rich-style terminal logging |
src/minidump.h | Automatic crash dump capture |
src/build_info.h | Build and system info capture |
src/rippled_debug.h | Single-include header (all of the above) |
tools/build-governor/ | .NET governor service |
scripts/setup-governor.ps1 | One-command governor setup |
scripts/build-rippled.ps1 | One-command rippled build |
patches/rippled_main.patch | Patch for Main.cpp |
examples/test_crash.cpp | Demo and test program |
- GitHub Repository
- rippled issue #6293 — the issue that inspired this toolkit
- rippled — the XRPL validator node