excuse me. I made a mistake. On Sat, Aug 27, 2016 at 2:28 PM, raziye deylamsalehi < [email protected]> wrote:
> Hi > > can anybody help me? > > > On Sat, Aug 27, 2016 at 3:04 AM, blindbouf rr <[email protected]> wrote: > >> hello >> I installed gem5 and ran dijkstra benchmark (of Mibench) but I saw below >> error: >> >> root@ubuntu:/home/blindbouf/gem5# ./build/ARM/gem5.opt >> --stats="/home/blindbouf/gem5/tests/test-progs/Mibench/dijkstra/dijkstra_small_stats.txt" >> configs/example/se.py -c /home/blindbouf/gem5/tests/tes >> t-progs/Mibench/dijkstra/dijkstra_small --options="/home/blindbouf/gem >> 5/tests/test-progs/Mibench/dijkstra/input.dat" > >> /home/blindbouf/gem5/tests/test-progs/Mibench/dijkstra/dijks >> tra_small_output.txt >> >> warn: DRAM device capacity (8192 Mbytes) does not match the address range >> assigned (512 Mbytes) >> >> fatal: Object file architecture does not match compiled ISA (ARM). >> >> @ tick 0 >> >> [create:build/ARM/sim/process.cc, line 669] >> >> Memory Usage: 656548 KBytes >> >> Program aborted at tick 0 >> >> --- BEGIN LIBC BACKTRACE --- >> >> ./build/ARM/gem5.opt(_Z15print_backtracev+0x28)[0x919a68] >> >> ./build/ARM/gem5.opt(_Z12abortHandleri+0x46)[0x9301e6] >> >> /lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10)[0x7facae9a1d10] >> >> /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7facad40a267] >> >> /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7facad40beca] >> >> ./build/ARM/gem5.opt(_Z15__exit_epilogueiPKcS0_iS0_+0x1f3)[0x9a4e53] >> >> ./build/ARM/gem5.opt(_Z8ccprintfIJ5FlagsItEEEvRSoPKcDpRKT_+0x0)[0x929fc0] >> >> ./build/ARM/gem5.opt(_ZN11LiveProcess6createEP17LiveProcessP >> arams+0x14d)[0x97c04d] >> >> ./build/ARM/gem5.opt[0x133297a] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x54cc)[0x7facaed43f0c] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x57d1)[0x7facaed44211] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x57d1)[0x7facaed44211] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x57d1)[0x7facaed44211] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x57d1)[0x7facaed44211] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x57d1)[0x7facaed44211] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x57d1)[0x7facaed44211] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x57d1)[0x7facaed44211] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x58dd)[0x7facaed4431d] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> e+0x19)[0x7facaed3e6d9] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x5abb)[0x7facaed444fb] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra >> meEx+0x57d1)[0x7facaed44211] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> eEx+0x820)[0x7facaed8ef80] >> >> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod >> e+0x19)[0x7facaed3e6d9] >> >> --- END LIBC BACKTRACE --- >> >> Aborted (core dumped) >> >> >> how can I fix this problem? please help me. >> >> Thanks >> >> >> _______________________________________________ >> 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
