Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: vanboxem.ruben@gmail.com
Cc: dje@google.com, gdb@sourceware.org, python-list@python.org
Subject: Re: Python enabled gdb on Windows and relocation
Date: Sat, 14 May 2011 09:30:00 -0000	[thread overview]
Message-ID: <83ei41fx4a.fsf@gnu.org> (raw)
In-Reply-To: <BANLkTinkEF5RUwDr=29c_QBdu=abcGNNCQ@mail.gmail.com>

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


  reply	other threads:[~2011-05-14  9:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTikrK8DJOEpACA_uUVdZx25P5pc1tA@mail.gmail.com>
2011-05-12 16:20 ` Ruben Van Boxem
2011-05-14  6:39   ` Doug Evans
2011-05-14  9:09     ` Ruben Van Boxem
2011-05-14  9:30       ` Eli Zaretskii [this message]
2011-05-14 10:10         ` Ruben Van Boxem
2011-05-14 18:38         ` Doug Evans
2011-05-14 18:31       ` Doug Evans
2011-05-14 18:40         ` Doug Evans
2011-05-15 12:30         ` Ruben Van Boxem
2011-05-15 13:27           ` Ruben Van Boxem
2011-05-15 16:12             ` Ruben Van Boxem
2011-05-17 16:32               ` Ruben Van Boxem
2011-05-17 20:52               ` Doug Evans
2011-06-09  2:04               ` Asm warrior
     [not found]                 ` <BANLkTimfNgaKWbZdN-YVz9Vs2UW6vKsfiQ@mail.gmail.com>
2011-06-09 12:09                   ` Ruben Van Boxem
2011-05-17 20:36             ` Doug Evans

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=83ei41fx4a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=python-list@python.org \
    --cc=vanboxem.ruben@gmail.com \
    /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