Hello everyone,

I am trying to implement a Prime+Probe attack in gem5 full system mode
using X86 MESI Two Level architecture. When I run the command line, the
process aborts and returns
"build/X86_MESI_Two_Level/base/loader/image_file_data.cc:54: panic: panic
condition sz != 2 occurred: Couldn't read magic bytes from object file"

Can anyone tell me how I can fix this issue?

The command line in terminal:
./build/X86_MESI_Two_Level/gem5.opt configs/example/fs.py --disk-image
/home/issacnewton/gem5/fsimage/ubuntu-test.img --kernel
/home/issacnewton/gem5/linux-6.0.9/

The full output:
gem5 Simulator System.  https://www.gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 version 22.0.0.2
gem5 compiled Nov 22 2022 12:14:42
gem5 started Nov 22 2022 12:45:00
gem5 executing on issacnewton-950XDB-951XDB-950XDY, pid 37367
command line: ./build/X86_MESI_Two_Level/gem5.opt configs/example/fs.py
--disk-image /home/issacnewton/gem5/fsimage/ubuntu-test.img --kernel
/home/issacnewton/gem5/linux-6.0.9/

Global frequency set at 1000000000000 ticks per second
warn: system.workload.acpi_description_table_pointer.rsdt adopting orphan
SimObject param 'entries'
warn: No dot file generated. Please install pydot to generate the dot file
and pdf.
build/X86_MESI_Two_Level/mem/dram_interface.cc:690: warn: DRAM device
capacity (8192 Mbytes) does not match the address range assigned (512
Mbytes)
build/X86_MESI_Two_Level/base/loader/image_file_data.cc:54: panic: panic
condition sz != 2 occurred: Couldn't read magic bytes from object file
Memory Usage: 105036 KBytes
Program aborted at tick 0
--- BEGIN LIBC BACKTRACE ---
./build/X86_MESI_Two_Level/gem5.opt(+0x17c08b0)[0x55f56fbf18b0]
./build/X86_MESI_Two_Level/gem5.opt(+0x17e4d6c)[0x55f56fc15d6c]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7fe73d52e520]
/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7fe73d582a7c]
/lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7fe73d52e476]
/lib/x86_64-linux-gnu/libc.so.6(abort+0xd3)[0x7fe73d5147f3]
./build/X86_MESI_Two_Level/gem5.opt(+0x431405)[0x55f56e862405]
./build/X86_MESI_Two_Level/gem5.opt(+0x1910cd1)[0x55f56fd41cd1]
./build/X86_MESI_Two_Level/gem5.opt(+0x19119e1)[0x55f56fd429e1]
./build/X86_MESI_Two_Level/gem5.opt(+0x17e8ea5)[0x55f56fc19ea5]
./build/X86_MESI_Two_Level/gem5.opt(+0x449f75)[0x55f56e87af75]
./build/X86_MESI_Two_Level/gem5.opt(+0x99bb75)[0x55f56edccb75]
./build/X86_MESI_Two_Level/gem5.opt(+0x4bbeb6)[0x55f56e8eceb6]
./build/X86_MESI_Two_Level/gem5.opt(+0x4be104)[0x55f56e8ef104]
./build/X86_MESI_Two_Level/gem5.opt(+0x4b09d2)[0x55f56e8e19d2]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x12b6d3)[0x7fe73e0526d3]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyObject_MakeTpCall+0x8c)[0x7fe73e00d1ac]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0xe765a)[0x7fe73e00e65a]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyEval_EvalFrameDefault+0x9d78)[0x7fe73dfa29b8]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1c681f)[0x7fe73e0ed81f]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0xe7618)[0x7fe73e00e618]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyEval_EvalFrameDefault+0x9d78)[0x7fe73dfa29b8]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1c681f)[0x7fe73e0ed81f]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0xe7618)[0x7fe73e00e618]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyEval_EvalFrameDefault+0x9d78)[0x7fe73dfa29b8]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1c681f)[0x7fe73e0ed81f]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0xe7618)[0x7fe73e00e618]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyEval_EvalFrameDefault+0x9d78)[0x7fe73dfa29b8]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1c681f)[0x7fe73e0ed81f]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0xe7618)[0x7fe73e00e618]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyEval_EvalFrameDefault+0x9d78)[0x7fe73dfa29b8]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x1c681f)[0x7fe73e0ed81f]
--- END LIBC BACKTRACE ---
Aborted (core dumped)

Thanks,
William Hua
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org

Reply via email to