Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #5357 > unrolled thread

Re: Python enabled gdb on Windows and relocation

Started byEli Zaretskii <eliz@gnu.org>
First post2011-05-14 12:29 +0300
Last post2011-05-14 12:29 +0300
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#5357 — Re: Python enabled gdb on Windows and relocation

FromEli Zaretskii <eliz@gnu.org>
Date2011-05-14 12:29 +0300
SubjectRe: Python enabled gdb on Windows and relocation
Message-ID<mailman.1542.1305365412.9059.python-list@python.org>
> 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.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web