From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 7/7] gdb: startup commands to control Python extension language
Date: Thu, 29 Apr 2021 10:35:07 +0100 [thread overview]
Message-ID: <20210429093507.GE2364578@embecosm.com> (raw)
In-Reply-To: <f4b440c9-3550-82a6-b96a-60a55ac0b9dd@suse.de>
* Tom de Vries <tdevries@suse.de> [2021-04-29 10:32:05 +0200]:
> On 4/22/21 11:02 PM, Andrew Burgess wrote:
> > +set python ignore-environment on|off
> > +show python ignore-environment
> > + When 'on', this causes GDB's builtin Python to ignore any
> > + environment variables that would otherwise effect how Python
>
> affect?
>
> > + behaves. This command needs to be added to an early initialization
> > + file (e.g. ~/.config/gdb/gdbearlyinit) in order to affect GDB.
> > +
> > +set python dont-write-bytecode auto|on|off
> > +show python dont-write-bytecode
> > + When 'on', this causes GDB's builtin Python to not write any
> > + byte-code (.pyc files) to disk. This command needs to be added to
> > + an early initialization file (e.g. ~/.config/gdb/gdbearlyinit) in
> > + order to affect GDB. When 'off' byte-code will always be written.
> > + When set to 'auto' (the default) Python will check the
> > + PYTHONDONTWRITEBYTECODE. environment variable.
>
> Dot at end of variable name.
Thanks for pointing out these two issues, I pushed the patch below as
obvious to address them.
Thanks,
Andrew
---
commit 8eb82ba1fdc052d2bb08ec6f0d98b8d2c10edd17
Author: Andrew Burgess <andrew.burgess@embecosm.com>
Date: Thu Apr 29 10:29:41 2021 +0100
gdb/NEWS: Fix typo and stray full stop
Some errors introduced in commit:
commit edeaceda7b2f33b2c3bf78c732e67f3188e7f0b9
Date: Thu Aug 27 16:53:13 2020 +0100
gdb: startup commands to control Python extension language
gdb/ChangeLog:
* NEWS: Fix typo and stray full stop.
diff --git a/gdb/NEWS b/gdb/NEWS
index 6550ea352ac..19cb444e7fe 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -109,7 +109,7 @@ show print type hex
set python ignore-environment on|off
show python ignore-environment
When 'on', this causes GDB's builtin Python to ignore any
- environment variables that would otherwise effect how Python
+ environment variables that would otherwise affect how Python
behaves. This command needs to be added to an early initialization
file (e.g. ~/.config/gdb/gdbearlyinit) in order to affect GDB.
@@ -120,7 +120,7 @@ show python dont-write-bytecode
an early initialization file (e.g. ~/.config/gdb/gdbearlyinit) in
order to affect GDB. When 'off' byte-code will always be written.
When set to 'auto' (the default) Python will check the
- PYTHONDONTWRITEBYTECODE. environment variable.
+ PYTHONDONTWRITEBYTECODE environment variable.
* Changed commands
next prev parent reply other threads:[~2021-04-29 9:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 21:02 [PATCH 0/7] New options to control how Python is initialized Andrew Burgess
2021-04-22 21:02 ` [PATCH 1/7] gdb: remove unused argument from gdb_init Andrew Burgess
2021-04-23 14:15 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 2/7] gdb: ensure SIGINT is set to SIG_DFL during initialisation Andrew Burgess
2021-04-23 14:16 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 3/7] gdb: delay python initialisation until gdbpy_finish_initialization Andrew Burgess
2021-04-23 14:26 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 4/7] gdb delay guile initialization until gdbscm_finish_initialization Andrew Burgess
2021-04-23 14:29 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 5/7] gdb: initialise extension languages after processing early startup files Andrew Burgess
2021-04-23 14:30 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 6/7] gdb: extension languages finish_initialization to initialize Andrew Burgess
2021-04-23 14:31 ` Tom Tromey
2021-04-22 21:02 ` [PATCH 7/7] gdb: startup commands to control Python extension language Andrew Burgess
2021-04-23 10:31 ` Eli Zaretskii
2021-04-23 14:32 ` Tom Tromey
2021-04-29 8:32 ` Tom de Vries
2021-04-29 9:35 ` Andrew Burgess [this message]
2021-04-29 9:46 ` Andrew Burgess
2021-04-29 10:08 ` Tom de Vries
2021-05-02 10:31 ` Andrew Burgess
2021-05-02 18:15 ` Tom de Vries
2021-04-29 12:17 ` Eli Zaretskii
2021-04-29 12:32 ` Eli Zaretskii
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=20210429093507.GE2364578@embecosm.com \
--to=andrew.burgess@embecosm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).