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

build(deps): update coretrace-stack-analyzer past v0.22.0, which does not finish on CoreTrace's own code

Open
  • Is something wrong?
#169 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
38/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
cmake, cpp
Domain
performance, tooling

Research direction

Start with cmake/stackUsageAnalyzer.cmake and src/Process/Tools/StackAnalyzerToolImplementation.cpp; the issue reports that v0.22.0 stalls in the ownership engine, while the analyzer's main completes much faster. Check the analyzer release and bridge API, then update the dependency and adapt the bridge if needed. Run the stated ctrace --compile-commands invocation on CoreTrace's database and confirm it completes in minutes; CI should stay green.

Written by the indexing model from the issue text.

Description

bug build severity/major

The stack analyzer pinned in cmake/stackUsageAnalyzer.cmake (v0.22.0) does not finish on CoreTrace's own code. Its main does, but no release contains the fix yet.

Observed

On f2672ac, macOS 15.6.1 on Apple M3, LLVM 20.1.2, with CoreTrace's 22 translation units (src/**/*.cpp, main.cpp):

Run v0.22.0 (through ctrace) main d7a58d6 (standalone)
Whole program, default options stopped after 42 min, unfinished 90 s
src/Process/Ipc/ApiHandler.cpp alone, --no-resource-cross-tu over 300 s 9 s
src/Process/Tools/StackAnalyzerToolImplementation.cpp alone, same over 300 s 4 s
src/App/Runner.cpp alone, same 142 s 6 s

A sample of the v0.22.0 runs shows the time in the ownership engine (ownership::solve, AbstractState::join, Contents::merge), on one core whatever --jobs (coretrace-stack-analyzer#199). ctrace cannot stop it: the linked analyzers take no timeout (docs/configuration.md).

main is 149 commits ahead of v0.22.0; coretrace-stack-analyzer#184 (closed 2026-10-08) is one of the related fixes.

To do

  • Release the stack analyzer from main (v0.23.0).
  • Update GIT_TAG in cmake/stackUsageAnalyzer.cmake, and adapt the bridge (src/Process/Tools/StackAnalyzerToolImplementation.cpp) if its API changed.

Acceptance

  • ctrace --compile-commands <CoreTrace's own database> --invoke ctrace_stack_analyzer completes, in minutes rather than hours.
  • CI stays green.

Found by the initial static analysis of CoreTrace on its own code (2026-10-13).

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.