Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to turn off core dump #16

Open
SaschaJohn opened this issue Aug 17, 2022 · 1 comment
Open

How to turn off core dump #16

SaschaJohn opened this issue Aug 17, 2022 · 1 comment
Labels
question Further information is requested

Comments

@SaschaJohn
Copy link

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

@umarcor umarcor added the question Further information is requested label May 25, 2024
@umarcor
Copy link
Member

umarcor commented May 25, 2024

I'm not sure about that. qemu-user-static seems to have option -d Activate 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants