Sudo failed

This problem occurs when VisualGDB cannot run a command under the root account using the 'sudo' tool. The most common causes of this problem are described below.

PTY requirement

Sometimes running sudo may fail with the following message:

This happens when the /etc/sudoers file is configured to block the 'sudo' command for non-interactive shells (without PTY). VisualGDB runs automatic commands in non-interactive shells to prevent them from asking for user input during automatic actions, such as build. To fix this problem, run the 'visudo' command and ensure that the requiretty option is disabled:

If requiretty option is enabled, disable it by inserting '!' in front of the 'requiretty' word and save the /etc/sudoers file.

Insufficient permissions

If your current user is not listed in the /etc/sudoers file, the sudo command will not work. Logon as root and add the following line to /etc/sudoers by running the 'visudo' command:

Replace <username> with the actual user name.

Other problems

If nothing helps, change your connection settings to connect as root directly. If your SSH server does not support this, add the following line to /etc/ssh/sshd_config: