andrew/libakerror
1
0
Fork 0
Code Issues 15 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Only ThreadSanitizer is wired into CI, not ASan/UBSan #3

New Issue
Open
opened 2026-08-02 18:59:05 -04:00 by tachikoma · 0 comments
tachikoma commented 2026-08-02 18:59:05 -04:00
Collaborator
Copy Link

Source: TODO.md §1 (at 5695061)

AKERR_SANITIZE builds the library and the tests with any sanitizer list, and CI
runs -DAKERR_SANITIZE=thread through scripts/thread_test.sh. Nothing runs
address,undefined yet, and that is the one that covers the original
motivation: mutation testing caught an out-of-bounds probe in the status-name
hash table that the suite could not, because the failure mode was a write into
adjacent BSS, which does not crash.

Sharpening one test closed that instance; ASan would catch the whole class
regardless of how sharp the assertions are.

The machinery is in place -- this is one more job in .gitea/workflows/ci.yaml
running cmake -S . -B build/asan -DAKERR_SANITIZE=address,undefined. Left
separate because ASan and TSan cannot be combined in one build.

Files: .gitea/workflows/ci.yaml

Filed by Tachikoma (Claude Code, Opus 5, 1M context)

**Source:** TODO.md §1 (at 5695061) `AKERR_SANITIZE` builds the library and the tests with any sanitizer list, and CI runs `-DAKERR_SANITIZE=thread` through `scripts/thread_test.sh`. **Nothing runs `address,undefined` yet, and that is the one that covers the original motivation:** mutation testing caught an out-of-bounds probe in the status-name hash table that the suite could not, because the failure mode was a write into adjacent BSS, **which does not crash.** Sharpening one test closed that instance; **ASan would catch the whole class regardless of how sharp the assertions are.** The machinery is in place -- this is one more job in `.gitea/workflows/ci.yaml` running `cmake -S . -B build/asan -DAKERR_SANITIZE=address,undefined`. Left separate because ASan and TSan cannot be combined in one build. **Files:** `.gitea/workflows/ci.yaml` --- Filed by Tachikoma (Claude Code, Opus 5, 1M context)
tachikoma added this to the 2.0.x milestone 2026-08-02 18:59:05 -04:00
tachikoma added the test-coverageblast-radius:mediumstatus::grooming labels 2026-08-02 18:59:05 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abi-break
Cannot land without a soname bump
 api-gap
A caller cannot express something
 blast-radius:high
Ordering: highest blast radius
 blast-radius:low
Ordering: lowest blast radius
 blast-radius:medium
Ordering: middling blast radius
 defect
Wrong behaviour reachable from the public API
 design-decision
Needs a decision written down before code
 docs
Documentation, comments, AGENTS.md
 hygiene
Style, dead code, consistency
 packaging
Build, install, pkg-config, CMake config
 performance
Has a measurement behind it
 status::blocked
Waiting on something else -- a decision, a dependency, or another issue
 status::grooming
Not yet worked out: scope, approach or priority still being settled
 status::ready
Understood well enough to start: scope and approach are settled
 test-coverage
A gap in the suites, not a defect
No Label blast-radius:medium status::grooming test-coverage
Milestone
No items
No Milestone 2.0.x
Projects
Clear projects
No project
Assignees
Clear assignees
tachikoma andrew
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: andrew/libakerror#3
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?