Hi Seems that you are using an old version (which exploit X86_SE) Have you tried with the latest one?
// Naderan *Mahmood; On Sat, May 12, 2012 at 9:56 PM, Nilay Vaish <[email protected]> wrote: > It seems GDB might be able to point out the place where the exception > occurred. > > -- > Nilay > > > On Sat, 12 May 2012, Muhammad Sulman wrote: > > Hi all, >> > > > I wrote following simple code before start testing with large code: > /* ----- test.cpp ----- */ > #include <iostream> > int main () { > for (unsigned int i = 0; i < 10; ++i) { > std::cout<<"i = "<<i<<std::endl; > > } > > return 0; > } > /* ------------------- */ > > However, I received the following error: > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc > > I'm using following following configuration: > ./gem5/build/X86_SE/gem5.**debug gem5/configs/example/se.py -c > testprg/test > > I'll be glad if somebody could help me with this. > > Thank you! > > -- > Best Regards, > Sulman > > _______________________________________________ > 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
