[Minor Feature] Instrumented libtcod debug build for sanitizer coverage #280
Labels
No labels
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
priority:tier1-active
priority:tier2-foundation
priority:tier3-future
priority:tier4-deferred
Refactoring & Cleanup
system:animation
system:documentation
system:grid
system:input
system:performance
system:procgen
system:python-binding
system:rendering
system:ui-hierarchy
Tiny Feature
workflow:blocked
workflow:needs-benchmark
workflow:needs-documentation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
john/McRogueFace#280
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
The debug build system (added post-7DRL 2026) instruments McRogueFace code with ASan/UBSan, but libtcod's pre-built release binaries in
__lib/are uninstrumented. libtcod's pathfinding and FOV operate directly on McRogueFace's grid data structures — the exact location of the #258–#263 heap overflow family.ASan can detect overflows in our code that corrupt their memory, but cannot detect bugs originating inside libtcod. Since we build libtcod from source anyway (
modules/libtcod-headless/), adding an instrumented build is straightforward.Proposal
Add libtcod to
tools/build_debug_python.sh(or a companiontools/build_debug_libs.sh) that:modules/libtcod-headless/with-fsanitize=address,undefined.soto__lib_debug/make asantarget already links against__lib_debug/first, so it would pick up the instrumented libtcod automaticallyValue
Related