Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
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 16:56:00 -0000	[thread overview]
Message-ID: <m3ipsmj1l3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201106011217.55915.vapier@gentoo.org> (Mike Frysinger's message	of "Wed, 1 Jun 2011 12:17:54 -0400")

>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:

Mike> i slapped this together.  what do you think (ignoring missing docs) ?

It seems reasonable to me overall, though see below.

Mike> +char **appendargv (char **argv, const char *arg, ...)

Wrong formatting.

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

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.

Tom


  reply	other threads:[~2011-06-03 16:56 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 [this message]
2011-06-03 18:34       ` Mike Frysinger

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=m3ipsmj1l3.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=toolchain-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.org \
    /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