Hi Gabe,
Thank you for the reply, I will try to see more with GDB. Interestingly,
same workload works in older version of gem5. We had Ubuntu 16 machines
with gem5 2016 version. If I use same work load with it's "se.py" and run,
the workload executes with any number of CPUs with out resulting in t
Hi Sachin. Without looking at the output, this sounds like a null pointer
to a structure or object within your workload, where the thing within being
accessed is at offset 0x14 from the start of the struct/object. You can use
GDB to debug code within gem5 using the remote GDB stub:
https://www.gem
Hi Gabe,
Thanks for the suggestion, it worked. I used "se.py" file and submitted
workload. It seems that for multithreaded work load, if number of threads
is equal to number of cores, things work. I used --debug flag to verify
whether both cores are running. But unfortunately, I have ran into anot
I'm not 100% sure this is right, but I think what you do is assign the same
process object to each core you want a thread to run on.
Gabe
On Mon, Nov 15, 2021 at 10:25 AM Sachin Vijay Kumar via gem5-users <
gem5-users@gem5.org> wrote:
> Hi all,
>
> I have some basic question about assigning a
