From: Bob Rossi <bob@brasko.net>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Check permissions of .gdbinit files
Date: Tue, 31 May 2005 14:42:00 -0000 [thread overview]
Message-ID: <20050531132742.GA12857@white> (raw)
In-Reply-To: <20050530230026.GA3618@nevyn.them.org>
On Mon, May 30, 2005 at 07:00:26PM -0400, Daniel Jacobowitz wrote:
> On Tue, May 31, 2005 at 12:49:05AM +0200, Andreas Schwab wrote:
> > If you have a group of developers working on the same project you might
> > want a shared .gdbinit somewhere.
>
> I'm leaning towards handling that by suggesting in the manual that you
> use "source .gdbinit" in $HOME/.gdbinit for that. I agree that it's a
> little less convenient. I dunno.
The really bad thing about this is that you can't source a generic path.
For instance, source $GROUP_GDB_INIT_DIR/.gdbinit
Make's it very hard to make the .gdbinit scripts configurable. For
instance, since this is for .gdbinit files that are typically not in
$HOME, you would probably have one for every program that is built (or
something like that). So if you were unfortunate enough to be effected
by this change, you would have to change your $HOME/.gdbinit path each
time to point to the .gdbinit you wanted to source. This would be
annoying.
What if we had GDB prompt the user to determine if they wanted to read
the .gdbinit file in? Then we could add another configuration variable
to GDB that allowed it to always read in the files. That way, by
default GDB would be more safe, but for the rest of us, it would work
the way it always has.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2005-05-31 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 19:41 Daniel Jacobowitz
2005-05-30 19:46 ` Nathan J. Williams
2005-05-30 19:53 ` Daniel Jacobowitz
2005-05-30 19:54 ` Nathan J. Williams
2005-05-30 19:55 ` Daniel Jacobowitz
2005-05-30 21:28 ` Jason Molenda
2005-05-30 22:29 ` Eli Zaretskii
2005-05-30 23:00 ` Daniel Jacobowitz
2005-05-31 13:52 ` Eli Zaretskii
2005-05-31 21:03 ` Christopher Faylor
[not found] ` <umzqb9kha.fsf@gnu.org>
[not found] ` <20050531222233.GF9864@trixie.casa.cgf.cx>
2005-06-02 3:51 ` Eli Zaretskii
2005-06-02 4:26 ` Christopher Faylor
2005-06-02 21:54 ` Eli Zaretskii
2005-05-30 22:42 ` Andreas Schwab
2005-05-30 22:49 ` Daniel Jacobowitz
2005-05-31 2:27 ` Andreas Schwab
2005-05-31 2:50 ` Daniel Jacobowitz
2005-05-31 14:42 ` Bob Rossi [this message]
2005-05-31 17:54 ` Stan Shebs
2005-06-11 22:35 ` Mark Kettenis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050531132742.GA12857@white \
--to=bob@brasko.net \
--cc=gdb-patches@sourceware.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox