[gem5-users] Spec2017 GCC segfaults while running fine natively

[muke101 via gem5-users]

Hi, I'm running simpoints of a custom compiled AArch64 GCC binary in gem5 to 
generate checkpoints. After collecting around half the checkpoints for one of 
the spec commands, it crashes with the following error:

`build/ARM/sim/faults.cc:102: panic: panic condition !handled && 
!tc->getSystemPtr()->trapToGdb(SIGSEGV, tc->contextId()) occurred: Page table 
fault when accessing virtual address 0x28fc8b160​`

This binary runs perfectly fine natively and under valgrind to collect the 
BBVs, so I assume this is a gem5 bug or a misconfiguration.

I'm running under SE mode with se.py and using NonCachingCPU.

Does anyone know where I can start looking to fix this, or have maybe seen it 
before?

Thanks.

Sent with [Proton Mail](https://proton.me/) secure email.
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org