From: "Tom de Vries (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: gdb-patches@sourceware.org
Cc: Christian Biesinger <cbiesinger@google.com>
Subject: Change in binutils-gdb[master]: [RFC][gdb] Make script-extension strict reject unknown extensions
Date: Mon, 14 Oct 2019 17:41:00 -0000 [thread overview]
Message-ID: <20191014174145.1F83C29ECF@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1571060583000.Ia357a4b0b1042808401578266da80919035ad576@gnutoolchain-gerrit.osci.io>
Tom de Vries has posted comments on this change. ( https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/40 )
Change subject: [RFC][gdb] Make script-extension strict reject unknown extensions
......................................................................
Patch Set 1:
> Patch Set 1:
>
> A couple questions about this:
> - If specified in -ix or a system gdbinit file, does it prevent reading ~/.gdbinit?
I marked ~/.gdbinit execution using:
...
$ cat ~/.gdbinit
python
print ("HERE")
...
And using this command I can see iex is executed after ~/.gdbinit:
...
$ gdb -q -batch -iex "echo bla1\n" -iex "set script-extension strict" -iex "echo bla2\n"
HERE
bla1
bla2
...
But for the system gdbinit, it's yes.
> - Does it prevent reading a file in --command if it doesn't have the extension?
Yes:
...
$ gdb -batch -q -ex "set script-extension strict" --command=bla.bla
Scripting in the "<UNKNOWN>" language is not supported in this copy of GDB.
....
--
To view, visit https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/40
To unsubscribe, or for help writing mail filters, visit https://gnutoolchain-gerrit.osci.io/r/settings
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: Ia357a4b0b1042808401578266da80919035ad576
Gerrit-Change-Number: 40
Gerrit-PatchSet: 1
Gerrit-Owner: Tom de Vries <tdevries@suse.de>
Gerrit-Reviewer: Tom de Vries <tdevries@suse.de>
Gerrit-CC: Christian Biesinger <cbiesinger@google.com>
Gerrit-Comment-Date: Mon, 14 Oct 2019 17:41:45 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
prev parent reply other threads:[~2019-10-14 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gerrit.1571060583000.Ia357a4b0b1042808401578266da80919035ad576@gnutoolchain-gerrit.osci.io>
2019-10-14 16:08 ` Christian Biesinger (Code Review)
2019-10-14 17:41 ` Tom de Vries (Code Review) [this message]
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=20191014174145.1F83C29ECF@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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