From: Eli Zaretskii <eliz@gnu.org>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [patch, doc RFA] gdb.parameter("directories"), new "set dir" command
Date: Thu, 04 Nov 2010 04:01:00 -0000 [thread overview]
Message-ID: <831v7168kw.fsf@gnu.org> (raw)
In-Reply-To: <20101104010740.1942E2460AB@ruffy.mtv.corp.google.com>
> Date: Wed, 3 Nov 2010 18:07:39 -0700 (PDT)
> From: dje@google.com (Doug Evans)
>
> This patch does two things.
> - make python gdb.parameter("directories") work
> - new command "set directories"
Thanks.
> *** Changes since GDB 7.2
>
> +* GDB has a new command: "set directories".
> + It is like the "dir" command except that it replaces the
> + source path list instead of augmenting it.
> +
> * Python scripting
>
> ** GDB values in Python are now callable if the value represents a
> @@ -25,6 +29,8 @@
> ** New commands "info pretty-printers", "enable pretty-printer" and
> "disable pretty-printer" have been added.
>
> + ** gdb.parameter("directories") is now available.
> +
> * C++ Improvements:
>
> ** GDB now puts template parameters in scope when debugging in an
This part is fine with me.
> +GDB ensures the search path always ends with $cdir:$cwd by\n\
> +appending these paths if necessary.\n\
^^^^^
"directories", not "paths", since the whole list is called "search
path".
> --- doc/gdb.texinfo 2 Nov 2010 22:44:12 -0000 1.771
> +++ doc/gdb.texinfo 4 Nov 2010 01:00:50 -0000
> @@ -6620,6 +6620,11 @@ Reset the source path to its default val
> @c RET-repeat for @code{directory} is explicitly disabled, but since
> @c repeating it would be a no-op we do not say that. (thanks to RMS)
>
> +@item set directories @var{path-list}
> +@kindex set directories
> +Set the source path to @var{path-list}.
> +@samp{$cdir:$cwd} are added if missing.
This part is OK.
next prev parent reply other threads:[~2010-11-04 4:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 1:07 Doug Evans
2010-11-04 4:01 ` Eli Zaretskii [this message]
2010-11-05 17:14 ` 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=831v7168kw.fsf@gnu.org \
--to=eliz@gnu.org \
--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