From: Andreas Schwab <schwab@linux-m68k.org>
To: Pedro Alves <palves@redhat.com>
Cc: Tristan Gingold <gingold@adacore.com>,
Jack Howarth <howarth@bromo.med.uc.edu>,
gdb@sourceware.org
Subject: Re: PR13901
Date: Mon, 02 Apr 2012 16:22:00 -0000 [thread overview]
Message-ID: <m2limeqf2j.fsf@igel.home> (raw)
In-Reply-To: <4F79C453.3030802@redhat.com> (Pedro Alves's message of "Mon, 02 Apr 2012 16:22:59 +0100")
Pedro Alves <palves@redhat.com> writes:
> 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.
You can handle that by calling the shell only for expanding the
arguments.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-04-02 16:22 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 ` PR13901 Pedro Alves
2012-04-02 16:22 ` Andreas Schwab [this message]
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=m2limeqf2j.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
--cc=howarth@bromo.med.uc.edu \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).