Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Windows process backend does not compile and the Windows port was reverted

Open
  • Is something wrong?
#54 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp
Domain
backend, ci-cd

Research direction

Read include/Process/WinProcess.hpp alongside the C4 Process interface and the existing Unix process backend; check the C4 and M6 dependencies first. Then build with _WIN32 and run the available process tests, and inspect the CI configuration for the Windows job. Done means Windows captures tool output and exit status, compiles WinProcess.hpp, and has a windows-latest build job when the analyzer permits.

Written by the indexing model from the issue text.

Description

enhancement severity/major

Problem

include/Process/WinProcess.hpp has a constructor incompatible with ProcessFactory, uses an undefined arguments member and hard-codes cmd /C dir. PR #36 (Windows port) was merged then reverted.

Fix

Re-align WindowsProcess on the new Process interface from C4 (CreateProcess with pipes, exit code). Add a Windows CI job once the analyzer builds on Windows. Depends on C4 and M6.

Acceptance

  • WinProcess.hpp compiles under _WIN32 against the C4 interface
  • Tool output and exit status are captured on Windows like on Unix
  • A windows-latest CI job builds ctrace (analyzer permitting)

Delivery

One focused PR with an English Conventional Commit. Include Closes #<this issue> in the PR body. Tracked in ROADMAP.md as M10.

Dominant language
C++
Stars
5
Forks
4
Avg merge
1h 4m
Merged PRs (30d)
71

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CoreTrace/coretrace

All issues in CoreTrace/coretrace

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.