Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH/RFC] new argv handlers to help with sim argv building
Date: Fri, 03 Jun 2011 18:34:00 -0000	[thread overview]
Message-ID: <201106031302.56937.vapier@gentoo.org> (raw)
In-Reply-To: <m3ipsmj1l3.fsf@fleche.redhat.com>

[-- Attachment #1: Type: Text/Plain, Size: 1032 bytes --]

On Friday, June 03, 2011 12:56:24 Tom Tromey wrote:
> >>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
> Mike> +char **appendargv (char **argv, const char *arg, ...)
> 
> Wrong formatting.

i dont know what you mean

> The canonical source for libiberty is gcc, so changes have to go there.

yes, but i'm just bouncing the idea right now

> Mike> +  argv = appendargv (argv, "--sysroot", gdb_sysroot, NULL);
> [...]
> Mike> +      uargv = gdb_buildargv (args);
> Mike> +      sim_argv = mergeargv (argv, uargv, NULL);
> Mike> +      freeargv (argv);
> 
> If there is only one argument potentially needing quoting from
> buildargv, and we have to do splitting and merging as well, then it
> seems like it would be simpler to just add a quoting function and use
> that.

quoting opens a whole can of worms i dont want to think about.  simply 
sticking quotes around gdb_sysroot doesnt solve the whole problem.  what if 
the sysroot has quotes in it ?  i'd prefer to stick in the argv world.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2011-06-03 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1306440200-25087-1-git-send-email-vapier__8251.52545371584$1306440225$gmane$org@gentoo.org>
2011-05-27 17:47 ` [PATCH] gdb: sim: automatically pass down sysroot Tom Tromey
2011-05-27 18:37   ` Mike Frysinger
2011-06-01 16:18   ` [PATCH/RFC] new argv handlers to help with sim argv building Mike Frysinger
2011-06-03 16:56     ` Tom Tromey
2011-06-03 18:34       ` Mike Frysinger [this message]

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=201106031302.56937.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=toolchain-devel@blackfin.uclinux.org \
    --cc=tromey@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