Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/c-testingEngenharia reversa 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 instalações+3 em 7 dias39 EstrelasMITsincronizado há 11 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
nJxH1wBDQN…CXxDlSCQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote6bd0ec7f…ea7eb3f4
6bd0ec7fb13c…0bd8ea7eb3f45 arquivos · ⁦6.1 KB⁩
VarreduraBaixo1 achado
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/coding/c-testing@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em 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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd5686bd0ec7fAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login