From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26021 invoked by alias); 27 May 2010 01:24:21 -0000 Received: (qmail 26006 invoked by uid 22791); 27 May 2010 01:24:20 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (74.125.121.35) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 27 May 2010 01:24:16 +0000 Received: from wpaz9.hot.corp.google.com (wpaz9.hot.corp.google.com [172.24.198.73]) by smtp-out.google.com with ESMTP id o4R1OCri005774 for ; Wed, 26 May 2010 18:24:13 -0700 Received: from pvg7 (pvg7.prod.google.com [10.241.210.135]) by wpaz9.hot.corp.google.com with ESMTP id o4R1OBKF008802 for ; Wed, 26 May 2010 18:24:11 -0700 Received: by pvg7 with SMTP id 7so1052855pvg.26 for ; Wed, 26 May 2010 18:24:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.87.41 with SMTP id k41mr7300458rvb.109.1274923450254; Wed, 26 May 2010 18:24:10 -0700 (PDT) Received: by 10.140.255.14 with HTTP; Wed, 26 May 2010 18:24:10 -0700 (PDT) In-Reply-To: <1274918921-23200-1-git-send-email-brobecker@adacore.com> References: <1274918921-23200-1-git-send-email-brobecker@adacore.com> Date: Thu, 27 May 2010 01:54:00 -0000 Message-ID: Subject: Re: Add support for the GDB Python Library From: Doug Evans To: Joel Brobecker Cc: gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2010-05/txt/msg00625.txt.bz2 On Wed, May 26, 2010 at 5:08 PM, Joel Brobecker wro= te: > Hello, > > One of the things that we still don't have in the FSF tree is a "GDB > Python Library" - that is a collection of standard Python scripts that > come with GDB. The idea is to help future contributions but setting > things up so that it's easy to add new python-based commands/functions/ > features, etc. > > This is what this couple of patches provide: > =A0- Patch #1: Defines a pythondir where the GDB Python library is > =A0 =A0expected to be found, and enhances the GDB/python support to > =A0 =A0look for them there. > =A0- Path #2: is built on top of patch #1, and provides the first > =A0 =A0such python patch. =A0We selected one form project archer that > =A0 =A0might be useful: pahole.py. Is there a reason to not make pythondir be $(GDB_DATADIR)/python or some su= ch? [I'm not sure to what extent .pyc files are architecture independent. Is that it?]