gdb error with .gdbinit

Red Squirrel

No Lifer
May 24, 2003
70,164
13,569
126
www.anyf.ca
I get this error when I try to do a gdb on a program:

Code:
warning: not using untrusted file "/data/sde/dev/.gdbinit"

Normally I can just change the permissions, but problem is, my dev folder is on a remote server via a samba share, so the permissions arn't local. I get access denied if I try to change the permissions.

Any way to bypass this error? I am running as root if it matters.
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
Don't run dev tools as root and don't keep those files on a CIFS share. You might be able to tweak the mount.cifs command to present permissions that gdb will like, but you might still end up hitting other issues caused by CIFS' unique handling of permissions, inode numbers, file locking, etc.
 

Red Squirrel

No Lifer
May 24, 2003
70,164
13,569
126
www.anyf.ca
I rather use cifs that way all my data is stored in one location, so I don't have to write backup scripts for every server, I just have one script that handles it all. Is there a way to make the server think the share is actually a regular device?

Also I need to use root, as with a regular user I wont have permission to do most tasks I need to get done. Constantly doing sudo gets old.
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
I rather use cifs that way all my data is stored in one location, so I don't have to write backup scripts for every server, I just have one script that handles it all. Is there a way to make the server think the share is actually a regular device?

Also I need to use root, as with a regular user I wont have permission to do most tasks I need to get done. Constantly doing sudo gets old.

If the server hosting them is Linux just use NFS. If not, then I'm not sure what to tell you.

And development shouldn't require root access unless you're debugging something like a daemon that listens on a privileged port or it's constantly messing with root-owned files and neither of those should probably be the case, maybe at release but not during development.