From: Vladimir Prus <vladimir@codesourcery.com>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: gdb@sources.redhat.com
Subject: Re: [MI] argv/argc/args
Date: Wed, 25 Jun 2008 17:28:00 -0000 [thread overview]
Message-ID: <200806252128.28815.vladimir@codesourcery.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA0429120A@ecamlmw720.eamcs.ericsson.se>
On Wednesday 25 June 2008 21:21:07 Marc Khouzam wrote:
> Hi,
>
> just to give input on DSF's use of these commands,
> although that doesn't speak for any other frontend.
>
> > -exec-next
> > -exec-next-instruction
> > -exec-step
> > -exec-step-instruction
> > -exec-continue
>
> DSF does use a parameter on some of these but it is only an integer.
> So, no problem here.
>
>
> > The bad ones are:
> >
> > -exec-until
>
> We use a parameter of format file:line
> I guess it could be a problem if the file name had a space in it.
>
> > -target-download
>
> Not used yet. But any future use will require to have some special
> code if we want to support older GDBs.
>
> > -target-select
> >
>
> The parameters here are host:port or serialDevice, which I believe
> will not contain spaces. Should be fine.
Well, it can also be "| some-program lots-of-parameters", so quoting
is an issue. (And Sourcery G++ does use that ;-)
> > 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?
>
> For DSF, it should mean no changes, so I like this solution.
Ok.
- Volodya
next prev parent reply other threads:[~2008-06-25 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806251907.58610.vladimir@codesourcery.com>
2008-06-25 17:21 ` Marc Khouzam
2008-06-25 17:28 ` Vladimir Prus [this message]
2008-06-25 9:06 Vladimir Prus
2008-06-25 14:45 ` Marc Khouzam
2008-06-27 13:53 ` Daniel Jacobowitz
2008-06-27 14:39 ` 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=200806252128.28815.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb@sources.redhat.com \
--cc=marc.khouzam@ericsson.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