Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeder.news-service.com!feeder3.cambriumusenet.nl!feed.tweaknews.nl!194.134.4.91.MISMATCH!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=nBnWF1BJDy9zKcCOjTNBTsbGFAhEoiwXH9FzqTcUA8IR6KRqDvXf5kQmhKXHOg4WHd ivk7JsazsVvq5t1qNWTQ==
MIME-Version: 1.0
In-Reply-To: <BANLkTimshMHOAnc2xtO=Vjvxg_oEZ0EUJA@mail.gmail.com>
References: <BANLkTikrK8DJOEpACA_uUVdZx25P5pc1tA@mail.gmail.com> <BANLkTimshMHOAnc2xtO=Vjvxg_oEZ0EUJA@mail.gmail.com>
Date: Fri, 13 May 2011 23:38:59 -0700
Subject: Re: Python enabled gdb on Windows and relocation
From: Doug Evans <dje@google.com>
To: vanboxem.ruben@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: gdb@sourceware.org, python-list@python.org
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.1539.1305355152.9059.python-list@python.org>
Lines: 67
NNTP-Posting-Host: 82.94.164.166
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:5339

On Thu, May 12, 2011 at 9:19 AM, Ruben Van Boxem
<vanboxem.ruben@gmail.com> wrote:
> (now in plain-text as required by gdb mailing list)
>
> Hi,
>
> I am currently trying to integrate Python support into my toolchain
> build (including GDB of course). It is a sysrooted
> binutils+GCC+GDB+mingw-w64 toolchain.
>
> I currently have the basic setup working: I can link gdb with my
> manually generated import lib to the python dll from the official
> Windows install. If there is anything I am missing or a very easy
> solution to the problems decsribed below, please just say so. I am
> only suggesting what I would like to happen.
>
> Now on to the problems I'd like to discuss:
>
> 1. gdb.exe won't start without me having set PYTHONPATH manually.

In a properly configured/built gdb on linux this isn't necessary, even
if python is installed in some random place.
I'm not sure about windows though.
Did you specify --with-python when you configured gdb, and if so did
you specify a value?
e.g., --with-python=3DSOME_VALUE

> I understand the need for this, but as gdb requires Python 2, and users
> of my toolchain may have installed Python 3 or a 32-bit version python
> they want to use from the same environment (without changing their own
> PYTHONPATH), there is no way to run python-enabled gdb.
> [...]

Yeah.
There is a proposal to add GDB_PYTHONPATH (or some such IIRC) and have
gdb use that instead of PYTHONPATH if it exists, but there's been
resistance to it.
I think(!) what would happen is that gdb would set $PYTHONPATH to the
value of $GDB_PYTHONPATH.
[Inferiors started by gdb should still get the original value of
PYTHONPATH though.]

> 2. With PYTHONPATH set as a temporary workaround, gdb starts, but
> spits out a traceback:
> Traceback (most recent call last):
> =A0 File "<string>", line 35, in <module>
> =A0 File "m:\development\mingw64\share\gdb/python/gdb/__init__.py", line
> 18, in <module>
> =A0=A0=A0 gdb.command.pretty_printers.register_pretty_printer_commands()
> =A0 File "m:\development\mingw64\share\gdb/python/gdb\command\pretty_prin=
ters.py",
> line 368, in register_pretty_printer_commands
> =A0=A0=A0 InfoPrettyPrinter()
> =A0 File "m:\development\mingw64\share\gdb/python/gdb\command\pretty_prin=
ters.py",
> line 100, in __init__
> =A0=A0=A0 gdb.COMMAND_DATA)
> RuntimeError: Could not find command prefix info.
>
> This is a minor problem I think, as "python import time" "python print
> time.clock()" works as expected. What is wrong?

I'm not sure.
The error message is complaining that the "info" command prefix doesn't exi=
st.
I don't see how that can happen as python is initialized long after
the info command is created.