Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Inputs: names starting with '-' become tool options, --static with --invoke runs a tool twice, missing inputs found late

Abierto
  • ¿Algo no está bien?
#190 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
50/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
cpp
Área
cli, devtools

Línea de trabajo

Start with src/Process/Tools/FlawfinderToolImplementation.cpp near line 18 and include/Process/Tools/AnalysisTools.hpp lines 212-213, where input paths are passed to tools without a -- separator, and compare with how the cppcheck and runtime-analyzer paths are built. Then find where --static and --invoke selections are combined, and check the input-resolution step for missing files and --compile-commands. Done means each acceptance item in the issue has a test: a -x.c input is analyzed, cppcheck runs once, and a missing path exits 1 with that path named.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug severity/minor

Three problems with how inputs reach the tools, found by the resilience campaign (docs/quality/resilience.md).

1. File names that start with - are read as options (C37)

ctrace --input ./-F.c --invoke flawfinder

The path is normalized to -F.c and passed to flawfinder as an argument, which reads it as an option: *** getopt error: option -. not recognized, exit 3. A repository can name its files freely, and flawfinder and ikos have options that write files. src/Process/Tools/FlawfinderToolImplementation.cpp:18 and include/Process/Tools/AnalysisTools.hpp:212-213 pass paths without a -- separator; cppcheck and tscancode use --file-list, and the runtime analyzer already passes --.

Fix: pass -- before the file paths, or ./ before a path that starts with -.

2. --static with --invoke runs a tool twice (C36)

ctrace --input ok.c --static --invoke cppcheck runs cppcheck twice and counts each of its findings twice.

Fix: merge the selections into one set of tools before running them.

3. Missing inputs are found late (C07, C08, C23)

A missing input file is passed to the tools, which fail: the run ends with exit 3, "cppcheck could not run", instead of saying that the file does not exist. A --compile-commands that does not exist gives "No input files resolved" without naming it.

Fix: check that each input exists before running any tool, and exit 1 naming the missing path.

Acceptance

  • An input named -x.c is analyzed by every tool.
  • --static --invoke cppcheck runs cppcheck once.
  • A missing input or compile database exits 1 with its path in the message.
  • A test for each.
Lenguaje dominante
C++
Estrellas
5
Forks
4
Merge medio
1 h 57 min
PR fusionados (30 d)
88

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CoreTrace/coretrace

Todos los issues de CoreTrace/coretrace

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.