From: Khoo Yit Phang <khooyp@cs.umd.edu>
To: Doug Evans <dje@google.com>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Make python/lib/gdb and submodules proper Python modules
Date: Fri, 07 Sep 2012 14:27:00 -0000 [thread overview]
Message-ID: <979CE4F9-537E-4FA0-893D-FDF19CB408F7@cs.umd.edu> (raw)
In-Reply-To: <CADPb22QniCQQMrE-Sgmo2UGwOHna=0ZgX2q+34sSnDgEFOuXVQ@mail.gmail.com>
Hi,
(Sorry for the resend again!)
On Sep 7, 2012, at 2:18 AM, Doug Evans wrote:
> On Sun, Sep 2, 2012 at 8:44 PM, Khoo Yit Phang <khooyp@cs.umd.edu> wrote:
>>
>> One caveat about this patch is that the data-directory must contain the
>> gdb module, otherwise Python will not be fully initialized (with a warning)
>> and Python support will be very limited (only the _gdb module will be
>> available).
>
> One thing that comes to mind is that, regardless of implementation
> details, we can't easily get rid of gdb.PYTHONDIR because it's part of
> the API gdb provides.
> [grep PYTHONDIR doc/gdb.texinfo]
It's pretty easy to restore PYTHONDIR if necessary, by computing it from gdb.__file__. I'm more concerned about the caveat about requiring the initial data-directory for Python. Is it common to change the data-directory, other than for testing GDB?
Yit
September 7, 2012
next prev parent reply other threads:[~2012-09-07 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 3:44 Khoo Yit Phang
2012-09-07 6:19 ` Doug Evans
2012-09-07 14:27 ` Khoo Yit Phang [this message]
2012-09-10 20:38 ` Tom Tromey
2012-09-12 20:00 ` Khoo Yit Phang
2012-09-13 20:56 ` Tom Tromey
2012-09-13 21:51 ` Khoo Yit Phang
2012-09-14 5:48 ` Regression for --batch [Re: [RFC] Make python/lib/gdb and submodules proper Python modules] Jan Kratochvil
2012-09-14 6:00 ` Khoo Yit Phang
2012-09-14 6:16 ` Jan Kratochvil
2012-09-14 6:26 ` Khoo Yit Phang
2012-09-14 6:37 ` Jan Kratochvil
2012-09-14 6:53 ` Khoo Yit Phang
2012-09-14 7:04 ` 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=979CE4F9-537E-4FA0-893D-FDF19CB408F7@cs.umd.edu \
--to=khooyp@cs.umd.edu \
--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