Not really :). If you know precisely what I should type, I'll do it. What really bugs me is that it was working with an older version of gem5. I have removed the build files and rebuilt it but with no luck.
Thank you for your help Mahmood. 2013/6/4 Mahmood Naderan <[email protected]> > Hi > bad_alloc() messages usually means running out of memory. You can > attach valgrind to find memory leakage. > > Hope that help > > On 6/4/13, Maxime Chéramy <[email protected]> wrote: > > Hi, > > > > I've just updated my instance of gem5 with the last changes from the > > mercurial repo. The code still compile properly but when I try to run a > > bench in SE mode, it crashes quickly: > > > > command line: build/X86/gem5.opt configs/example/se.py -n 1 > > --cpu-type=timing --caches --l2cache --l1d_size=256B --l1d_assoc=4 > > --l1i_size=256B --l1i_assoc=4 --l2_size=16kB --l2_assoc=4 > --num-l2caches=1 > > -c /home/max/bench/automotive/basicmath/basicmath_small > > Global frequency set at 1000000000000 ticks per second > > terminate called after throwing an instance of 'std::bad_alloc' > > what(): std::bad_alloc > > Program aborted at cycle 0 > > > > My last update was the 28th of February and the exact same command line > was > > working (I still have a copy of the directory before the update). > > > > > > Do you have any opinion or suggestion? I have not tried yet "scons -c", I > > am rebuilding currently. > > > > > > Regards, > > > > Maxime. > > > > > -- > Regards, > Mahmood > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
