This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch 2/2] Implement multi-component --with-auto-load-dir
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 9 May 2012 13:17:43 -0700
- Subject: Re: [patch 2/2] Implement multi-component --with-auto-load-dir
- References: <20120509154847.GB12692@host2.jankratochvil.net>
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