strau0106
strau0106
If you are at it, I'd also take a copy 😛
Quickly confirming this also happens on your provided docker image verilator/verilator latest (v5.026) and v5.024
This issue also occurs when using the verilator from debian apt repos. Furthermore I realised this is the only file where I am fst dumping. Could that be the issue?...
Okay, I made some progress. It only crashes in the docker conainer because I only let google test export a report in the docker container for gitlab to show it...
Nothing to do with docker anymore and the logs directory exists. i let verilator create it: ``` Verilated::commandArgs(argc, argv); testing::InitGoogleTest(&argc, argv); auto res = RUN_ALL_TESTS(); Verilated::mkdir("logs"); VerilatedCov::write("logs/cpu.dat"); return res; ```...
Infact, if I let my main thread sleep, ``` int main(int argc, char** argv) { Verilated::commandArgs(argc, argv); testing::InitGoogleTest(&argc, argv); auto res = RUN_ALL_TESTS(); std::this_thread::sleep_for(std::chrono::seconds(1));std::this_thread::sleep_for(std::chrono::seconds(1)); Verilated::mkdir("logs"); VerilatedCov::write("logs/cpu.dat"); return res; } ```...
@wsnyder I am now simply observing that coverage files are empty when using timing functions. Any clues?
Yes no coverage points. m_items in VerilatedCovImp... ill investigate further
Aw man i know whats going on now, I do contextp.reset() to restart time and with that i loose my coveragepoints. @wsnyder any other way to start time at 0...