From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: pkoning@equallogic.com
Cc: drow@false.org, gdb@sourceware.org
Subject: Re: Quoting, backslashes, CLI and MI
Date: Thu, 23 Feb 2006 04:25:00 -0000 [thread overview]
Message-ID: <200602222059.k1MKxAGI030568@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <17404.49729.275843.669493@gargle.gargle.HOWL> (message from Paul Koning on Wed, 22 Feb 2006 14:57:53 -0500)
> Date: Wed, 22 Feb 2006 14:57:53 -0500
> From: Paul Koning <pkoning@equallogic.com>
>
> (Hm... should there be a flavor of "set args" that does shell-style
> expansion of the args list? That sure would be handy for cases where
> I want to debug a program that's being handed a wildcard, or some
> similar expanded argument, and I end up having to expand it manually
> when inside GDB...)
But we already have that flavor of "set args"; it's what "set args"
;-). When we start an inferior process, we do so by starting a shell,
which will expand the argument list for you.
Mark
next prev parent reply other threads:[~2006-02-22 20:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 4:30 Daniel Jacobowitz
2006-02-22 4:35 ` Paul Koning
2006-02-22 19:57 ` Daniel Jacobowitz
2006-02-22 21:57 ` Paul Koning
2006-02-23 4:25 ` Mark Kettenis [this message]
2006-02-25 1:30 ` Eli Zaretskii
2006-02-22 4:40 ` Eli Zaretskii
2006-02-22 5:24 ` Daniel Jacobowitz
2006-02-22 19:30 ` Eli Zaretskii
2006-02-22 20:59 ` Daniel Jacobowitz
2006-02-22 17:39 ` Jim Blandy
2006-02-22 18:01 ` Daniel Jacobowitz
2006-02-22 18:05 ` Jim Blandy
2006-02-22 18:11 ` Daniel Jacobowitz
2006-02-22 19:24 ` Andrew STUBBS
2006-02-22 19:28 ` Daniel Jacobowitz
2006-02-22 19:50 ` Eli Zaretskii
2006-02-22 19:34 ` Eli Zaretskii
2006-02-22 19:53 ` Daniel Jacobowitz
2006-02-23 11:13 ` Eli Zaretskii
2006-02-22 19:25 ` Eli Zaretskii
2006-02-22 19:51 ` Daniel Jacobowitz
2006-02-23 4:32 ` Eli Zaretskii
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=200602222059.k1MKxAGI030568@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pkoning@equallogic.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