Ubuntu – How to work around sudo ‘segmentation fault’ on basic bash commands


I am sure the answers are out there, but alas there are too many answers (here and elsewhere) to other questions stopping me from finding them. I just encountered something substantially similar to what is described at the closed SO question, sudo : “segmentation fault” Ubuntu maverick [closed].

My team is using Ubuntu 11.04 on VMWare Workstation 8.0.4. We are doing development using c++, Xenomai, Qt, and Qt Creator. When we simulate our application on the virtual machine, we currently need to launch Qt Creator with sudo. My colleague mentioned today that he has been having issues where his workstation locks up and he needs to restart and that occasionally he has the issue that all sudo bash commands return "segmentation fault".

I just ran our application in simulation mode. I was running Qt Creator under sudo and Qt Creator received the signal abort (if I recall). Afterward, every command executed with sudo from sudo qtcreator to sudo ls resulted in the message Segmentation fault. I clicked on the power widget to see if I could log out, but the system shut down straightaway without prompting.

My understanding is that we run sudo because of a permissions issue with Xenomai and the VM as currently configured, but my colleague has a workaround for this. I expect that not running Qt Creator under sudo — something that has always made me nervous — will help contain this issue, but I find it troubling that this could happen and manifest as it does.

Does anyone know what is happening? Any recommendations on how to work around this issue?

This is happening often to I am trying tolobby for VM changes to be able to run the process without sudo.

Best Answer

There is not a single answer to this problem other than it has probably to do with lack of memory. Try to see what free -m outputs and go from there. Adding swap space might solve the problem if you don't have enough.

Related Question