From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21853 invoked by alias); 9 May 2012 20:18:06 -0000 Received: (qmail 21843 invoked by uid 22791); 9 May 2012 20:18:04 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 09 May 2012 20:17:51 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 0EB461C6766; Wed, 9 May 2012 16:17:51 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YCPaw3dBkd53; Wed, 9 May 2012 16:17:50 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id D01FF1C6756; Wed, 9 May 2012 16:17:50 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 2349D145616; Wed, 9 May 2012 13:17:43 -0700 (PDT) Date: Wed, 09 May 2012 20:18:00 -0000 From: Joel Brobecker To: Jan Kratochvil Cc: gdb-patches@sourceware.org Subject: Re: [patch 2/2] Implement multi-component --with-auto-load-dir Message-ID: <20120509201743.GL15555@adacore.com> References: <20120509154847.GB12692@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120509154847.GB12692@host2.jankratochvil.net> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2012-05/txt/msg00314.txt.bz2 Hi Jan, > currently GDB has hard-coded GDB_DATADIR/auto-load for the auto-loaded > scripts. The problem is one may need more of such directories as you may have > multiple package sets / packages on the same system in different > subdirectories overriding each other in some order. > > Therefore created 'set auto-load scripts-directory' for it. I really do not understand what this new setting is about. Can you just give me a quick concrete example of what wouldn't work with the current code, and how this gets solved by the new setting? I was hoping at some point that this would allow us to have auto-loaded scripts without having to have the same path structure in the auto-load directory as in the executable (by that, I mean that if you are debugging /work/build/gcc-feature-a/gcc/cc1, you don't need to have cc1-gdb.gdb defined in your auto-load directory as auto-load/work/build/gcc-feature-a/gcc/cc1-gdb.gdb. It'd just be sufficient to have cc1-gdb.gdb defined in your scripts-directory. But looking at the code, I don't think that this is what we are talking about. -- Joel