From: Daniel Jacobowitz <drow@false.org>
To: "Nathan J. Williams" <nathanw@wasabisystems.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Check permissions of .gdbinit files
Date: Mon, 30 May 2005 19:55:00 -0000 [thread overview]
Message-ID: <20050530195356.GA31201@nevyn.them.org> (raw)
In-Reply-To: <mtu3bs4fqeu.fsf@scrubbing-bubbles.mit.edu>
On Mon, May 30, 2005 at 03:46:17PM -0400, Nathan J. Williams wrote:
> Daniel Jacobowitz <drow@false.org> writes:
>
> > > I think the "owned by a different user" change is problematic. I've
> > > used build systems that autogenerated .gdbinit files in the build
> > > tree, and it would be entirely sensible for one developer to go and
> > > debug another developer's build.
> >
> > Well that's the whole point. You'll get a warning; would you be
> > happier if the warning explicitly suggested "source .gdbinit"?
>
> I guess. I think I don't agree that this is a problem that needs
> solving, fundamentally.
I'm not completely sure that I disagree. But it's worth talking about
at least. Here's the problem case:
<user> Foo is broken!
<root> What do you want me to do about it?
<user> Well, there's a core dump in /blah.
<root> OK
# cd /blah
# gdb /bin/foo core
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-linux".
Hi!
You have been owned.
(gdb)
I wouldn't expect GDB to execute code in that case, but it does.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-30 19:54 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 [this message]
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
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=20050530195356.GA31201@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nathanw@wasabisystems.com \
/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