Re: [gem5-users] Debugging std::bad_alloc memory errors in gem5

2020-03-25 Thread Subhankar Pal
Thank you, Ciro. Turned out that by disabling most of the (classic) cache stat handlers, I was able to free up a lot of memory. Subhankar Pal | PhD Candidate, CSE | University of Michigan On March 25, 2020 at 4:38:52 AM, Ciro Santilli (ciro.santi...@gmail.com) wrote: I would try to put print

Re: [gem5-users] Debugging std::bad_alloc memory errors in gem5

2020-03-25 Thread Ciro Santilli
I would try to put prints/PDB on src/python/m5/stats/__init__.py where enable is called. On Wed, Mar 25, 2020 at 5:35 AM Subhankar Pal wrote: > > Hi, > > I am trying to run simulations in SE mode with a 1000+ (simple) cores. I get > the following error once m5.instantiate() is called. > Tracebac

[gem5-users] Debugging std::bad_alloc memory errors in gem5

2020-03-24 Thread Subhankar Pal
Hi, I am trying to run simulations in SE mode with a 1000+ (simple) cores. I get the following error once m5.instantiate() is called. Traceback (most recent call last): File "", line 1, in File "/home/subh/gem5/src/python/m5/main.py", line 436, in main exec filecode in scope File “confi