From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 9600@debbugs.gnu.org, rms@gnu.org, svenjoac@gmx.de
Subject: bug#9600: 24.0.50; .gdbinit does not run
Date: Mon, 26 Sep 2011 04:02:11 -0400 [thread overview]
Message-ID: <E1R868h-0006fl-CJ@fencepost.gnu.org> (raw)
In-Reply-To: <7sty7z3gth.fsf@fencepost.gnu.org> (message from Glenn Morris on Mon, 26 Sep 2011 03:26:18 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: rms@gnu.org, 9600@debbugs.gnu.org, svenjoac@gmx.de
> Date: Mon, 26 Sep 2011 03:26:18 -0400
>
> AFAICS, rms still has not said what the permissions of his gdbinit file
> were, beyond "writable". It seems this must mean "world-writable".
Most probably, because this is what I have in my bzr branches. I
guess that's because of umask, see below.
> I tested with Debian testing's gdb "7.3-debian". A gdbinit file writable
> by me was fine, a world-writable gdbinit was rejected with
>
> warning: not using untrusted file ".gdbinit"
Stock GDB does not reject such a .gdbinit. That was the gist of what
I was saying.
> This seems entirely reasonable to me
It was sufficiently controversial at the time to not make it into the
official GDB.
> Since I hope that everyone building Emacs from source does not use
> `umask 000'
I do, FWIW. Don't ask me why, it's something I have in my .bash_login
since about forever.
> I don't think any Emacs changes are needed.
No Emacs changes are needed in any case, since RMS can chmod the file,
and bzr will not touch the write mode bits.
next prev parent reply other threads:[~2011-09-26 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 17:34 bug#9600: 24.0.50; .gdbinit does not run Richard Stallman
2011-09-25 18:04 ` Eli Zaretskii
2011-09-25 18:22 ` Sven Joachim
2011-09-25 20:01 ` Eli Zaretskii
2011-09-26 1:00 ` Richard Stallman
2011-09-26 2:59 ` Eli Zaretskii
2011-09-26 7:26 ` Glenn Morris
2011-09-26 8:02 ` Eli Zaretskii [this message]
2011-09-26 8:13 ` Glenn Morris
2011-09-26 10:42 ` Richard Stallman
2011-09-26 16:30 ` Glenn Morris
2011-09-26 16:35 ` Glenn Morris
2011-09-26 21:13 ` Richard Stallman
2011-09-26 11:16 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1R868h-0006fl-CJ@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=9600@debbugs.gnu.org \
--cc=rgm@gnu.org \
--cc=rms@gnu.org \
--cc=svenjoac@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).