[gem5-users] Running gem5.opt via GDB

2021-09-19 Thread walt_90--- via gem5-users
Hello, I was trying to run gem5.opt using gdb Any suggestion how I can fix the following error that I got: Program received signal SIGTRAP, Trace/breakpoint trap.0x75d3d2a7 in kill () at ../sysdeps/unix/syscall-template.S:7878 ../sysdeps/unix/syscall-template.S: No such file or directory

[gem5-users] Re: Running gem5.opt via GDB

2021-09-19 Thread walt_90--- via gem5-users
Hi, I also get the following error: Program received signal SIGSEGV, Segmentation fault.0x55c32f5b in gem5::ArmISA::SupervisorCall::invoke (this=, tc=0x59c28520, inst=...)    at build/ARM/arch/arm/faults.cc:871871     tc->getSystemPtr()->workload->syscall(tc); Regards. On Sunday

[gem5-users] syscall perf_event_open (#241) unimplemented

2021-09-22 Thread walt_90--- via gem5-users
I got the following error while trying to run a binary with se.py build/ARM/sim/syscall_emul.cc:66: fatal: syscall perf_event_open (#241) unimplemented.Memory Usage: 703864 KBytes I am using the latest version of gem5 on Ubuntu 18.04. I read the related threads titled: [gem5-users] Using perf_eve

[gem5-users] Re: syscall perf_event_open (#241) unimplemented

2021-09-23 Thread walt_90--- via gem5-users
simulation (the patch you are referring to is providing visibility of the PMU to the linux kernel), But the syscall in SE mode is still un-implemented. Kind Regards Giacomo > -Original Message- > From: walt_90--- via gem5-users > Sent: 22 September 2021 20:06 > To: Gem5 U