while (*command) {

    result = PyRun_String(*command, Py_file_input, dict, dict);

    if (!result) {

        PyErr_Print();

        return 1;

    }

    Py_DECREF(result);




    command++;

Hello everyone, I'm currently attempting to replicate some previous work. I'm using gem5 version 20.0.3 and conducting experiments in gem5's Full System (fs) mode. Here's my command line. sudo build/ARM/gem5.opt ./configs/example/fs.py --disk-image=/home/lyq/gem5/benchmark/itecgo/itecgo/expand-aarch64-ubuntu-trusty-headless.img --kernel=/home/lyq/gem5/benchmark/itecgo/itecgo/vmlinux.euler --bootloader=/home/lyq/gem5/benchmark/itecgo/boot.arm64 --cpu-type=O3_ARM_v7a_3 –caches However, when I ended the simulation (after one hour) and examined state.txt, I found that only 26 instructions had been simulated. I attempted to debug and discovered that the program halted at line 67 in main.cc, specifically at the point of the "ret = m5Main(argc, argv)" call to the m5Main function. Within the init.cc file, the issue seems to be arising from the m5Main function. while (*command) { result = PyRun_String(*command, Py_file_input, dict, dict); if (!result) { PyErr_Print(); return 1; } Py_DECREF(result); command++; } When the program reaches the statement "result = PyRun_String(*command, Py_file_input, dict, dict);" for the second time, the program stops. There are no further step options in VSCode, and after that, it stops and restarts, and the variables on the left-hand side also disappear. Before entering this statement, the variables are displayed as follows: *command=0xaaaaad181040 "m5.main()" Py_file_input is defined as #define Py_file_input 257 in python.h Dict points to an address. When running this statement, the console outputs: warn: Existing EnergyCtrl, but no enabled DVFSHandler found. info: Entering event queue @ 0. Starting simulation... warn: SCReg: Access to unknown device dcc0:site0:pos0:fn7:dev0, which is similar to the normal simulation start output. However, when checking later, it seems that the program gets stuck at this point without any error. Does anyone have any clues? I'm not sure what to check. I've verified the compiled versions, including Python version 3.8.10, GCC version gcc (Ubuntu/Linaro 7.5.0-6ubuntu2) 7.5.0, clang version 10.0.0-4ubuntu1, and SCons version v3.1.2. If you need more debug information, please let me know, and I'll provide it as soon as possible. Thanks, Heyubin