Hi,
Thanks for you reply.
The executanle ('test') runs to completion when I run it separately in
terminal. However, when I test it under X86_SE it generates the aforementioned
error.
--
B.R.
Sulman
________________________________
From: Nilay Vaish <[email protected]>
To: Muhammad Sulman <[email protected]>; gem5 users mailing list
<[email protected]>
Sent: Saturday, May 12, 2012 7:26 PM
Subject: Re: [gem5-users] GEM5 generates 'bad_alloc' for a custom program
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
