Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Implement multi-component --with-auto-load-dir
Date: Wed, 09 May 2012 20:34:00 -0000	[thread overview]
Message-ID: <20120509203350.GA15551@host2.jankratochvil.net> (raw)
In-Reply-To: <20120509201743.GL15555@adacore.com>

Hi Joel,

On Wed, 09 May 2012 22:17:43 +0200, Joel Brobecker wrote:
> 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?

With Fedora scl-utils ("alternative packaging") you have both regular
	/usr/share/gdb/auto-load/
and also the "alternative"
	/opt/rh/upgradeset/root/usr/share/gdb/auto-load/

as there is both regular GDB and the "upgradeset" (=newer) GDB.
While for example libstdc++ Pretty Printers is located in both
(coincidentally, because it is bundled with GDB in some versions):
	/usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.16-gdb.py
	/opt/rh/upgradeset/root/usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.16-gdb.py

with the latter variant having more recent GDB macros and therefore preferred
by newer GDB located in
	/opt/rh/upgradeset/root/usr/bin/gdb
which is using its default configured
	/opt/rh/upgradeset/root/usr/share/gdb/auto-load/

it will be a problem that
	/usr/share/gdb/auto-load/lib64/libglib-2.0.so.0.3000.3-gdb.py

is not loaded at all because it does not have any "upgradeset" variant in
	/opt/rh/upgradeset/root/usr/share/gdb/auto-load/
.

This means we need multiple auto-load/ directories (unless we want to
introduce some shell scripting symlinks magic etc.).


> 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.

I do not think these two features are related.  I can think about some ideas
but I do not see a super-elegant one for it now.


Thanks,
Jan


  reply	other threads:[~2012-05-09 20:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 15:49 Jan Kratochvil
2012-05-09 17:50 ` Eli Zaretskii
2012-05-09 18:04   ` Jan Kratochvil
2012-05-09 18:45     ` Eli Zaretskii
2012-05-09 18:44   ` [doc patch] path vs. directory separator [Re: [patch 2/2] Implement multi-component --with-auto-load-dir] Jan Kratochvil
2012-05-09 19:21     ` Eli Zaretskii
2012-05-09 19:30       ` [commit] " Jan Kratochvil
2012-05-09 18:55   ` [patch 2/2] Implement multi-component --with-auto-load-dir Jan Kratochvil
2012-05-09 19:23     ` Eli Zaretskii
2012-05-11 18:21     ` [commit] " Jan Kratochvil
2012-05-09 20:18 ` Joel Brobecker
2012-05-09 20:34   ` Jan Kratochvil [this message]
2012-05-09 20:51     ` Joel Brobecker
2012-05-11 18:47       ` Jan Kratochvil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120509203350.GA15551@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox