From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-39198-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 12744 invoked by alias); 14 May 2011 09:30:22 -0000
Received: (qmail 12730 invoked by uid 22791); 14 May 2011 09:30:21 -0000
X-SWARE-Spam-Status: No, hits=-0.5 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_WEB,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 14 May 2011 09:30:05 +0000
Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0LL600J00ID3A800@a-mtaout23.012.net.il> for gdb@sourceware.org; Sat, 14 May 2011 12:30:03 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([77.124.10.122]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LL600JEUIE11L80@a-mtaout23.012.net.il>; Sat, 14 May 2011 12:30:03 +0300 (IDT)
Date: Sat, 14 May 2011 09:30:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Python enabled gdb on Windows and relocation
In-reply-to: <BANLkTinkEF5RUwDr=29c_QBdu=abcGNNCQ@mail.gmail.com>
To: vanboxem.ruben@gmail.com
Cc: dje@google.com, gdb@sourceware.org, python-list@python.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83ei41fx4a.fsf@gnu.org>
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>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2011-05/txt/msg00059.txt.bz2

> 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.