Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/c-testingReverse engineering e fuzzing

c-testing

⁨C testing workflow for unit and integration tests: deterministic harnesses, CMake/CTest execution strategy, sanitizer-first debugging, and fuzzing escalation. Use when writing or fixing tests for C (C11+) modules, stabilizing flaky suites, or reproducing memory/UB bugs.⁩

v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 StelleMITsincronizzato 11 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/c-testing

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
nJxH1wBDQN…CXxDlSCQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto6bd0ec7f…ea7eb3f4
6bd0ec7fb13c…0bd8ea7eb3f45 file · ⁦6.1 KB⁩
ScansioneBasso1 segnalazione
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/AeonDave/malskill/tree/main/coding/c-testing@21cd568

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

Pragmatic workflow for reliable C tests and bug-finding.

When to activate

  • Adding unit tests for C functions
  • Building a small test harness around a module
  • Debugging failing tests or memory corruption
  • Enabling sanitizers or fuzzing to reproduce crashes

Core rules

  • Keep unit tests deterministic and isolated.
  • Avoid real network/time in unit tests.
  • Run ASan/UBSan in CI for memory and UB signal.
  • Reproduce failures in the smallest possible command first.
  • Do not hide memory/UB bugs behind test-only flags, retries, or inflated timeouts.
  • Pair with test-driven-development when implementing persistent code or bug fixes test-first.
  • Pair with testing-reliability for fixture/timing anti-patterns and systematic-debugging when the root cause is unclear.

Phase 1 — Reproduce with smallest scope

  • Run the single failing test first (ctest -R ... or direct binary invocation).
  • Capture exact command, seed/input, and environment variables.
  • Eliminate unrelated test noise before debugging.

Phase 2 — Strengthen harness determinism

  • Keep each test independent (no shared mutable global state).
  • Use explicit fixtures/setup-teardown for temp files and state reset.
  • Prefer table-driven tests for parsers and boundary-heavy functions.

Phase 3 — Sanitizer-first diagnosis

  • Run AddressSanitizer for memory corruption/UAF/OOB.
  • Run UndefinedBehaviorSanitizer for integer/shift/null/alignment UB.
  • Use stack-symbolized reports before stepping into debugger.

Phase 4 — CTest execution strategy

  • Label tests (unit, integration, slow, flaky) and run by label.
  • Use --output-on-failure and --rerun-failed in local loops.
  • Add per-test TIMEOUT to avoid hanging pipelines.

Phase 5 — Fuzzing escalation

  • Add libFuzzer target for parser/decoder/validator style APIs.
  • Seed corpus with valid and invalid minimal inputs.
  • Keep fuzz target stateless, deterministic, and side-effect free.

Fast triage checklist

  • Single failing test reproduced in isolation.
  • Failure reproduced under sanitizer build (if memory/UB suspected).
  • Backtrace/symbolization points to root cause function.
  • Regression test added for the fixed bug.
  • Full suite rerun (or label-targeted suite if justified) with no new failures.

Resources

Load on demand:

  • references/harness.md — harness structure, assertions, Unity/cmocka options
  • references/cmake-ctest.md — CMake/CTest patterns, labels, sanitizer presets, MinGW cross-compile
  • references/sanitizers-fuzzing.md — ASan/UBSan usage and a minimal fuzz target outline
  • references/debugging.md — gdb/lldb, Valgrind, MinGW objdump/nm, MSVC dumpbin/WinDbg, ASan env vars

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.11.13-21cd56813 nov 202621cd5686bd0ec7fFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login