Hermit launches linux x86_64 programs in a special, hermetically isolated sandbox to control their execution. Hermit translates normal, nondeterministic behavior, into deterministic, repeatable behavior. This can be used for various applications, including replay-debugging, reproducible artifacts, chaos mode concurrency testing and bug analysis.
...
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 85
model name : Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz
stepping : 4
microcode : 0x2006d05
cpu MHz : 800.098
...
Additional context
Log file (renamed to .txt but it is really an .xz compressed log file) run.log.xz.txt
I see frequent cases of reverie_ptrace::task: [5] handle_signal: received signal SIGSEGV in the log -- I'm guessing it's not normal? But it seems to be so often, it's surprising that it wasn't fatal.
Describe the bug
hermit
panics while running a test case.Indicate any of these common scenarios that apply:
Environment
/proc/cpuinfo excerpt Xeon Silver 4114:
Additional context
Log file (renamed to .txt but it is really an .xz compressed log file) run.log.xz.txt
Add any other context about the problem here.