public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Tristan Gingold <gingold@adacore.com>,
	       Jack Howarth <howarth@bromo.med.uc.edu>,
	gdb@sourceware.org
Subject: Re: PR13901
Date: Mon, 02 Apr 2012 15:23:00 -0000	[thread overview]
Message-ID: <4F79C453.3030802@redhat.com> (raw)
In-Reply-To: <m2ty12i3ip.fsf@linux-m68k.org>

On 04/02/2012 03:58 PM, Andreas Schwab wrote:

> Pedro Alves <palves@redhat.com> writes:
> 
>> I'd be glad to see STARTUP_WITH_SHELL turned into a run-time option.  I think there's
>> a PR open for that even.  However, we need the shell at least for argument globbing,
>> as in, e.g., debugging `ls *', so I don't think we could make it off by default,
>> which practically renders it an orthogonal feature.
> 
> It's actually redirections that are problematic case here (argument
> expansions could be implemented completely independent from starting the
> inferior).


We can't make GDB fully compatible in all cases with what it can do today
if we skip the shell completely.  E.g., with "set args $(foo)", "$(foo)" is
expanded by the shell, and what that means is up to the user's shell.
That may mean "invoke the 'foo' program", as in "$(ls)" with sh.
So I'd even inclined to have !STARTUP_WITH_SHELL end up with no
argument expansion (as today).

So, if we made STARTUP_WITH_SHELL a runtime option, and even if we
defaulted it to off, we'd still need to make target code account for
when the user toggled the setting on.  So I still claim that that
would be an orthogonal feature, and that GDB should avoid touching
the SHELL process -- it should just PTRACE_CONT it, and nothing else.

-- 
Pedro Alves

  parent reply	other threads:[~2012-04-02 15:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 13:42 PR13901 Jack Howarth
2012-03-30 14:19 ` PR13901 Tristan Gingold
2012-04-02 10:44 ` PR13901 Tristan Gingold
2012-04-02 11:57   ` PR13901 Tristan Gingold
2012-04-02 13:17     ` PR13901 Jack Howarth
2012-04-02 13:22       ` PR13901 Tristan Gingold
2012-04-02 13:56     ` PR13901 Pedro Alves
2012-04-02 14:07       ` PR13901 Tristan Gingold
2012-04-02 14:17         ` PR13901 Pedro Alves
2012-04-02 14:25           ` PR13901 Tristan Gingold
2012-04-02 14:59           ` PR13901 Andreas Schwab
2012-04-02 15:08             ` PR13901 Tristan Gingold
2012-04-02 15:23             ` Pedro Alves [this message]
2012-04-02 16:22               ` PR13901 Andreas Schwab
2012-04-02 16:31                 ` PR13901 Pedro Alves
2012-04-02 17:28                   ` PR13901 Andreas Schwab
2012-04-03  7:28       ` PR13901 John Gilmore
2012-04-04 14:23         ` PR13901 Pedro Alves
2012-04-04 14:47           ` PR13901 Tristan Gingold
2012-04-04 15:01             ` PR13901 Pedro Alves

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=4F79C453.3030802@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=howarth@bromo.med.uc.edu \
    --cc=schwab@linux-m68k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).