From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32192 invoked by alias); 10 Nov 2011 13:15:16 -0000 Received: (qmail 32166 invoked by uid 22791); 10 Nov 2011 13:15:14 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from kay.astro.Princeton.EDU (HELO mail.astro.princeton.edu) (128.112.24.221) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 Nov 2011 13:14:59 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.astro.princeton.edu (Postfix) with ESMTP id ADCF91BC0060E for ; Thu, 10 Nov 2011 08:14:58 -0500 (EST) Received: from mail.astro.princeton.edu ([127.0.0.1]) by localhost (kay.astro.princeton.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BFnLe04g6Pfv for ; Thu, 10 Nov 2011 08:14:58 -0500 (EST) X-Submitted: to mail.astro.princeton.edu (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: rhl) with ESMTP for ; Thu, 10 Nov 2011 08:14:58 -0500 (EST) From: Robert Lupton the Good Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Problem writing python tests without installing Date: Thu, 10 Nov 2011 13:15:00 -0000 Message-Id: To: gdb@sourceware.org Mime-Version: 1.0 (Apple Message framework v1251.1) 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-11/txt/msg00076.txt.bz2 When running the testsuite, the python files that are sourced are apparentl= y e.g. gdb/testsuite/../data-directory/python/gdb/printing.py rather than gdb/python/lib/gdb/printing.py although the binary is as expected gdb/gdb The files appear to be installed by "make install". This is another manife= station of the problem that you cannot apparently work on the gdb python co= de without first installing it (away from it's cvs home -- but that can be = faked with a link...) Is there a proper way to work around this? R P.S. I wasted a lot of time on this... the final trick was=20 runtest -v -v -v and gdb_test_no_output "python import gdb.printing"=20 gdb_test_no_output "python raise RuntimeError(gdb.printing.__file__)"=20 to get the path. Sigh.