On 17/05/2014 01:35, Dimitri John Ledkov wrote: > On 16 May 2014 07:26, Charl Wentzel <charl.went...@vodamail.co.za> wrote:
>> I wanted do to debugging in Eclipse which required me to let Eclipse run >> gdb with sudo. However, for this to work, sudo must not ask for a >> password. So I've added the following entry in /etc/sudoers under the >> appropriate comment: > If you simply want to grant unrestricted permissions for gdb to attach > to any process, you don't need to grant full sudo to it. Thanks, I'll have a look into it. > Are there any other reasons why you want to run gdb as root from eclipse? Yes, I'm writing an application that works with /dev/port for setting IO states. I've looked into a few options, but none of the quite suited me: 1. Run Eclipse as root Running a program as root tends to mess up your config as permissions on config files sometimes end up with root permissions. Also, this means I can't write/debug that app inside Eclipse with my other programs, I'll have to run two instances of Eclipse instead of just one. 2. Using remote debugging You could start the debugger from the command line eg. "sudo gdb <my app>" and then connect to it from Eclipse via remote debugging. This just complicates the process, I want to have the ease of a IDE. So allowing Eclipse to start the debugger as root was the best and easiest solution so far. Charl -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
