Hi, You are getting this error because your benchmark's binary contains this syscall (setitimer) which is unimplemented in gem5. Looking into syscall_emul.cc will give you a better idea. If your benchmark's functionality does not depend much on this syscall you might be able to continue simulation after putting a hack in syscall_emul.cc file (i.e. don't terminate simualtion on this particular syscall). But, you will have to be careful about the simulation results (again depends what your benchmark is trying to do with this syscall).
See the following FAQ on Gem5's website: http://www.m5sim.org/Frequently_Asked_Questions#When_running_my_program_I_get_an_error_.22Error:_syscall_.3Csyscall_name_here.3E_unimplemented..22 Hope this will help. On Sat, Jun 25, 2016 at 4:53 AM, Faeze Banitaba <banitaba_...@yahoo.com> wrote: > Hi all, > > While running my benchmark on gem5 SE mode, i got this error, which > there's not enough documents about it over the site and i have no > familiarity with setitimer/getitimer as well. > > fatal: syscall setitimer (#104) unimplemented. > @ tick 17578000 > [unimplementedFunc:build/ARM/sim/syscall_emul.cc, line 95] > > Could anyone help me with this, please? > > Best Regards > > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
