From: Daniel Jacobowitz <dan@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Don't install gdb.PYTHONDIR if -nx
Date: Tue, 30 Nov 2010 04:22:00 -0000 [thread overview]
Message-ID: <20101130042206.GA1206@caradoc.them.org> (raw)
In-Reply-To: <20101129003949.502FC246199@ruffy.mtv.corp.google.com>
On Sun, Nov 28, 2010 at 04:39:49PM -0800, Doug Evans wrote:
> Hi.
>
> I was testing a change to gdb/command/pretty_printers.py
> and was tripping over the fact that gdb was picking up
> the installed copies.
> The testsuite loads the copies from the build dir, but
> python keeps the one already installed during gdb startup.
>
> This patch only installs gdb.PYTHONDIR (and only runs
> gdb/__init__.py which installs the python-based gdb commands)
> if not running with -nx.
If this is the problem you're trying to solve, I think a new option is
better - but it's not -np. Why not an option to set gdb.PYTHONDIR
before loading anything?
That said, -np may be useful too. But at that point it becomes more
of a question whether it should be part of -nx.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-11-30 4:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 0:40 Doug Evans
2010-11-29 21:38 ` Tom Tromey
2010-11-30 0:03 ` [RFA, doc RFA] " Doug Evans
2010-11-30 0:30 ` Jan Kratochvil
2010-11-30 3:54 ` Eli Zaretskii
2010-11-30 4:11 ` Doug Evans
2010-11-30 11:20 ` Eli Zaretskii
2010-11-30 15:29 ` Doug Evans
2010-11-30 18:59 ` Tom Tromey
2010-12-06 20:43 ` Doug Evans
2010-12-06 20:50 ` Eli Zaretskii
2010-12-06 20:58 ` Doug Evans
2010-12-06 21:15 ` Eli Zaretskii
2010-12-06 21:16 ` Doug Evans
2010-12-06 22:17 ` Doug Evans
2010-12-07 4:02 ` Eli Zaretskii
2010-12-06 21:15 ` Doug Evans
2010-12-07 1:38 ` Jan Kratochvil
2010-11-30 4:22 ` Daniel Jacobowitz [this message]
2010-11-30 5:16 ` [RFA] " Doug Evans
2010-11-30 18:19 ` Daniel Jacobowitz
2010-11-30 18:25 ` Doug Evans
2010-11-30 5:33 ` Jan Kratochvil
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=20101130042206.GA1206@caradoc.them.org \
--to=dan@codesourcery.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