From: Simon Marchi <simark@simark.ca>
To: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Documentation for Python -P commandline support
Date: Mon, 22 Jul 2019 16:04:00 -0000 [thread overview]
Message-ID: <03a80f5c-f816-bb02-0453-92b97ec7156a@simark.ca> (raw)
In-Reply-To: <20190721235427.21893-2-kevinb@redhat.com>
On 2019-07-21 7:54 p.m., Kevin Buettner wrote:
> gdb/doc/ChangeLog:
>
> * gdb.texinfo (Mode Options): Add documentation for -P.
> ---
> gdb/doc/gdb.texinfo | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index eddd939869..868a1734de 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -1252,6 +1252,16 @@ for remote debugging.
> Run using @var{device} for your program's standard input and output.
> @c FIXME: kingdon thinks there is more to -tty. Investigate.
>
> +@item -P
> +@cindex @code{-P}
> +@itemx --python
> +@cindex @code{--python}
> +Change interpretation of command line so that the argument immediately
> +following this switch is taken to be the name of a Python script file.
> +This option stops option processing; subsequent options are passed to
> +Python as @code{sys.argv}. This option is only available if Python
> +scripting support was enabled when @value{GDBN} was configured.
> +
> @c resolve the situation of these eventually
> @item -tui
> @cindex @code{--tui}
>
I think having an example would be helpful to understand how to use this
feature, and how it differs from -x. It wasn't really obvious to me at first,
so I suspect it won't be for other people less familiar with GDB.
Simon
next prev parent reply other threads:[~2019-07-22 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 23:54 [PATCH 0/3] Add -P command line switch for executing Python scripts Kevin Buettner
2019-07-21 23:54 ` [PATCH 1/3] Documentation for Python -P commandline support Kevin Buettner
2019-07-22 14:42 ` Eli Zaretskii
2019-07-22 16:04 ` Simon Marchi [this message]
2019-07-21 23:54 ` [PATCH 2/3] Add -P command line switch for executing Python scripts Kevin Buettner
2019-07-23 2:47 ` Simon Marchi
2019-07-23 20:25 ` Tom Tromey
2019-07-27 20:47 ` Kevin Buettner
2019-08-21 16:39 ` Pedro Alves
2019-07-21 23:54 ` [PATCH 3/3] Tests for Python -P commandline support Kevin Buettner
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=03a80f5c-f816-bb02-0453-92b97ec7156a@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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