From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7559 invoked by alias); 12 Aug 2011 18:49:41 -0000 Received: (qmail 7551 invoked by uid 22791); 12 Aug 2011 18:49:40 -0000 X-SWARE-Spam-Status: No, hits=-7.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Aug 2011 18:49:21 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p7CInKUD021964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 12 Aug 2011 14:49:20 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p7CInJi2017857; Fri, 12 Aug 2011 14:49:20 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p7CInIM4016421; Fri, 12 Aug 2011 14:49:18 -0400 From: Tom Tromey To: PcX Cc: pmuldoon@redhat.com, gdb@sourceware.org Subject: Re: How can I set gdb.python directory on Windows? References: <4E4136C5.1080704@gmail.com> <4E419F38.5070208@gmail.com> <4E454954.3010002@gmail.com> Date: Fri, 12 Aug 2011 18:49:00 -0000 In-Reply-To: <4E454954.3010002@gmail.com> (PcX's message of "Fri, 12 Aug 2011 23:40:04 +0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-08/txt/msg00035.txt.bz2 >>>>> "PcX" == PcX writes: PcX> As I type "python print gdb.PYTHONDIR" in gdb command, it will output: PcX> c:\mingw\share\gdb/python PcX> But my gdb python pretty printer directory is PcX> "e:\mypack\mingw\share\gdb\python". PcX> Is this a windows specific problem? I don't know. I think you will probably have to debug it if you want an answer. Tom