Re: [gem5-users] RISC-V DerivO3CPU: Assertion `atomicOpFunctor != NULL' failed

Hi Hossein, I'm glad you were able to find a solution to your problem. The best way to post code and try to get it merged is to create a patch on Gerrit , which is the patch review system gem5 uses. The CONTRIBUTING file has instructions on how to do that,

Re: [gem5-users] Remote gdb debug interface for RISCV/gem5.debug

Hi John, The GDB you're using should be fine. Your error is most likely a bug in the GDB implementation in the RISC-V ISA within gem5. I can take a look at it over the next week or so, but if you find a fix for it yourself don't hesitate to submit a patch. -Alec Roelke On Wed, Jul 17, 2019 at

Re: [gem5-users] Full system simulation freeze

Hello, I tried the patch and the problem persists. As *Shehab Elsayed* said, the problem is more likely to arise when the number of CPUs increases. For me, the simulation ends with only *one CPU* and I have to set a large *L2cache_size (4MB)* for the simulation to end with *2 CPUs*. From *3 CPUs*