Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Add -s option to source command.
Date: Sat, 17 Apr 2010 15:20:00 -0000	[thread overview]
Message-ID: <i2g6dc9ffc81004170819q7a419333mb78775d0cec8ab3f@mail.gmail.com> (raw)
In-Reply-To: <20100406215751.7EC1784397@ruffy.mtv.corp.google.com>

On Tue, Apr 6, 2010 at 2:57 PM, Doug Evans <dje@google.com> wrote:
> Hi.
>
> In a big source tree with multiple disparate components it's useful to be
> able to load scripts without having to type full path names.
>
> This patch adds a -s option to the source command to make it search
> for the script in the source search path even if the script name specifies
> a directory.
> For example, adding the top level source directory to the source search path
> lets one load scripts from any component by only typing the path from
> the top directory.
>
> I thought of simply extending the source command to do the search anyway
> but the current code explicitly doesn't do that to make "./foo" only mean
> "foo" in the current directory.  Granted, the comment (see openp) is
> referring to executables, but it's not clear to me it shouldn't also
> apply to scripts.  Plus, "source /absolute/path" should probably not
> scan the search path by default.
> So I went with adding an option.
>
> This patch also does a minor reorg of find_and_open_script so that
> it's useful in a subsequent patch I'll be submitting.
> I think the reorg is useful in itself, e.g. removing the from_tty
> arg to find_and_open_script, so I've including it here.
>
> Included are doc and testcase additions.
>
> Ok to check in?
>
> 2010-04-06  Doug Evans  <dje@google.com>
>
>        Add -s option to source command.
>        * cli/cli-cmds.c (find_and_open_script): Add function comment.
>        Delete from_tty and cleanupp args.  Split filep arg into file and
>        full_pathp.  New arg search_path.
>        (source_script_from_stream): New function.
>        (source_script_with_search): New function.
>        (source_script): Rewrite.
>        (source_command): Parse "-s" option.
>        (init_cli_cmds): Add "-s" docs to source command help.
>        * python/python.c (source_python_script): Make file arg a const char *.
>        Don't call fclose, leave for caller.
>        * python/python.h (source_python_script): Update.
>
>        testsuite/
>        * gdb.base/source-test.gdb: New file.
>        * gdb.base/source.exp: Add tests for "source -v" and "source -s".
>
>        doc/
>        * gdb.texinfo (Command Files): Add docs for new "source -s" option.
>

This caused:

help source^M
Read commands from a file named FILE.^M
^M
Usage: source [-s] [-v] FILE^M
-s: search for the script in the source search path,^M
    even if FILE contains directories.^M
-v: each command in FILE is echoed as it is executed.^M
^M
Note that the file ".gdbinit" is read automatically in this way^M
when GDB is started.^M
(gdb) FAIL: gdb.base/help.exp: help source



-- 
H.J.


  parent reply	other threads:[~2010-04-17 15:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 21:58 Doug Evans
2010-04-06 23:17 ` Doug Evans
2010-04-07 20:14 ` Tom Tromey
2010-04-08 22:49   ` Doug Evans
2010-04-08 23:09     ` Sergio Durigan Junior
2010-04-09  0:13       ` Doug Evans
2010-04-09 17:15       ` Tom Tromey
2010-04-09 17:48         ` Eli Zaretskii
2010-04-10  1:29         ` Joel Brobecker
2010-04-09  7:49     ` Eli Zaretskii
2010-04-09 17:23       ` Doug Evans
2010-04-09 17:46         ` Eli Zaretskii
2010-04-09 18:12           ` Doug Evans
2010-04-09 19:31             ` Eli Zaretskii
2010-04-09 19:49               ` Doug Evans
2010-04-12 17:31                 ` Doug Evans
2010-04-12 17:33                   ` Doug Evans
2010-04-12 17:47                     ` Tom Tromey
2010-04-12 17:54                   ` Eli Zaretskii
2010-04-14 22:01               ` Doug Evans
2010-04-15  3:10                 ` Eli Zaretskii
2010-04-09 17:13     ` Tom Tromey
2010-04-09 17:15       ` Doug Evans
2010-04-09 17:19         ` Tom Tromey
2010-04-17 15:20 ` H.J. Lu [this message]
2010-04-20  5:38   ` Doug Evans

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=i2g6dc9ffc81004170819q7a419333mb78775d0cec8ab3f@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.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