google / google/xls

Fuzzer crash 2026-09-14_ce8a

Open
#4,980 0 comments 0 reactions 0 assignees View on GitHub
fuzz 🧑‍🌾 gardener
Dominant language
C++
Stars
1.9k
Forks
283
Avg merge
2d 10h
Merged PRs (30d)
135

Description

Repro:

```
bazel test -c opt //xls/fuzzer:run_crasher_test_2026-09-14_ce8a
```

Error message:

```
Error: NOT_FOUND: Output `out`, instance #127 holds X value in Verilog simulator output.
=== Source Location Trace: ===
xls/simulation/module_testbench.cc:370
xls/simulation/module_testbench.cc:456
xls/simulation/module_simulator.cc:510
xls/simulation/module_simulator.cc:550
xls/tools/simulate_module_main.cc:208

```

Contributor guide

Open the contributing guide

Research direction

Start by running bazel test -c opt //xls/fuzzer:run_crasher_test_2026-09-14_ce8a and inspect the reported trace, beginning with xls/simulation/module_testbench.cc and xls/simulation/module_simulator.cc. Determine why the Verilog simulator output contains an X for instance #127, then verify that the crasher test completes without the NOT_FOUND error.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
compilers, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.