Re: Python enabled gdb on Windows and relocation

Date	2011-05-14 12:29 +0300
From	Eli Zaretskii <eliz@gnu.org>
Subject	Re: Python enabled gdb on Windows and relocation
References	<BANLkTikrK8DJOEpACA_uUVdZx25P5pc1tA@mail.gmail.com> <BANLkTimshMHOAnc2xtO=Vjvxg_oEZ0EUJA@mail.gmail.com> <BANLkTi=2xwRJmHfDBULRHidJUecMi0ix+w@mail.gmail.com> <BANLkTinkEF5RUwDr=29c_QBdu=abcGNNCQ@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.1542.1305365412.9059.python-list@python.org> (permalink)

Show all headers | View raw

> Date: Sat, 14 May 2011 11:09:13 +0200
> From: Ruben Van Boxem <vanboxem.ruben@gmail.com>
> Cc: gdb@sourceware.org, python-list@python.org
> 
> 1. Check hardcoded path; my suggestion would be "<gdb executable>/../lib/python27"
> 2. If this fails to find the necessary files/scripts, find it like you
> described above in Linux, without PYTHONPATH set.
> 3. Check PYTHONPATH.
> 
> I would think only number one would change, and perhaps be only
> enabled with a special configure option. Nothing else would have to
> change, and Windows users would rejoice :)

The problem, I think, is that it's not so easy on Unix to get the
place where the GDB executable leaves.  There isn't a system call to
do that (similar to what Windows gives you).

So I think on Posix platforms, number 2 would be used most of the
time.

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Python enabled gdb on Windows and relocation Eli Zaretskii <eliz@gnu.org> - 2011-05-14 12:29 +0300

csiph-web