You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running an amd64 container on Raspberry 4 (armv7l).
Running a particular binary in that container raises a "Segmentation fault" which is the same running it in a native amd64 environment.
Each time the "Segmentation fault" occurs, a core dump is created for that binary:
Segmentation fault (core dumped) e.g. qemu_L_H0JDGCZAZ_20220817-085108_146.core
Can I configure qus in a way not to create those core dumps?
Thanks in advance
Best
Sascha
The text was updated successfully, but these errors were encountered:
I'm not sure about that. qemu-user-static seems to have option -dActivate log (logfile=/tmp/qemu.log), I don't know if that will avoid printing content to the terminal.
So, you can try calling the qemu-user-static binary explicitly and using that option. If that works as expected, we can then guess how to pass that option to qus for it to be used when registering the interpeter.
Hello,
I'm running an amd64 container on Raspberry 4 (armv7l).
Running a particular binary in that container raises a "Segmentation fault" which is the same running it in a native amd64 environment.
Each time the "Segmentation fault" occurs, a core dump is created for that binary:
Segmentation fault (core dumped) e.g. qemu_L_H0JDGCZAZ_20220817-085108_146.core
Can I configure qus in a way not to create those core dumps?
Thanks in advance
Best
Sascha
The text was updated successfully, but these errors were encountered: