Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: [MI] argv/argc/args
Date: Fri, 27 Jun 2008 13:53:00 -0000	[thread overview]
Message-ID: <20080627135328.GA26625@caradoc.them.org> (raw)
In-Reply-To: <200806251306.27720.vladimir@codesourcery.com>

On Wed, Jun 25, 2008 at 01:06:27PM +0400, Vladimir Prus wrote:
> So, we have 3 commands for which requiring the input to be quoted per MI rules
> will cause issues; and fixing those issues will require changing other parts of
> GDB to avoid parsing filenames, which is risky at this point. It appears, that
> instead of reverting my original patch, we can just path those 3 commands
> via CLI directly. Does the plan sound reasonable?

Can we use the same approach for -exec-run/-exec-return now that some
of your other async-related patches are in?  I know it's less likely,
but we can't rule out some frontend using them.

For -target-select, -target-download, and -exec-until your approach
sounds great to me.  We do want these things to be quoted normally
someday but I think it has to wait for mi3.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2008-06-27 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  9:06 Vladimir Prus
2008-06-25 14:45 ` Marc Khouzam
2008-06-27 13:53 ` Daniel Jacobowitz [this message]
2008-06-27 14:39   ` Vladimir Prus
     [not found] <200806251907.58610.vladimir@codesourcery.com>
2008-06-25 17:21 ` Marc Khouzam
2008-06-25 17:28   ` Vladimir Prus

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=20080627135328.GA26625@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=vladimir@codesourcery.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