Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Cc: Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [PATCH v3 2/2] compile: Add 'set compile-gcc'
Date: Mon, 27 Apr 2015 15:47:00 -0000	[thread overview]
Message-ID: <553E5A1E.5000003@redhat.com> (raw)
In-Reply-To: <20150423210815.GA8626@host1.jankratochvil.net>

On 04/23/2015 10:08 PM, Jan Kratochvil wrote:

> @@ -688,4 +704,14 @@ String quoting is parsed like in shell, for example:\n\
>  			 " -fno-stack-protector"
>    );
>    set_compile_args (compile_args, 0, NULL);
> +
> +  add_setshow_filename_cmd ("compile-gcc", class_support,
> +			    &compile_gcc,
> +			    _("Set compile command GCC driver filename"),
> +			    _("Show compile command GCC driver filename"),
> +			    _("\
> +It should be absolute pathname to the gcc executable.\n\
> +If empty the default target triplet will be searched in $PATH."),
> +			    NULL, show_compile_gcc, &setlist, &showlist);
> +  compile_gcc = xstrdup ("");

...

> +@table @code
> +@item set compile-gcc
> +@cindex compile command driver filename override
> +Set compilation command used for compiling and injecting code with the
> +@code{compile} commands.  If this option is not set (it is set to
> +an empty string), the search described above will occur --- that is the
> +default.
> +

IIUC, gdb will always apply the same search as when this is set
empty?  That is, the user can also set this to a regex.  So it seems to me
that the documentation (manual and help) doesn't match the implementation?

Thanks,
Pedro Alves


  reply	other threads:[~2015-04-27 15:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 20:34 [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename Jan Kratochvil
2015-04-23 20:34 ` [PATCH v2 2/2] compile: Add 'set compile-gcc' Jan Kratochvil
2015-04-23 21:08   ` [PATCH v3 " Jan Kratochvil
2015-04-27 15:47     ` Pedro Alves [this message]
2015-04-27 17:54       ` Jan Kratochvil
2015-04-27 19:55         ` Pedro Alves
2015-04-27 15:31 ` [PATCH v2 1/2] compile: set debug compile: Display GCC driver filename Pedro Alves
2015-04-27 16:48   ` Jan Kratochvil
2015-04-27 17:19     ` Pedro Alves
2015-04-27 17:52       ` Jan Kratochvil
2015-04-27 19:17         ` Pedro Alves
2015-04-27 20:44           ` Jan Kratochvil
2015-04-27 20:50           ` Jan Kratochvil
2015-04-27 21:49             ` Phil Muldoon

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=553E5A1E.5000003@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pmuldoon@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