From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Add system-gdbinit infrastructure
Date: Tue, 18 Dec 2012 18:06:00 -0000 [thread overview]
Message-ID: <20121218180555.GL3273@adacore.com> (raw)
In-Reply-To: <20121218172002.GA24430@host2.jankratochvil.net>
> You two files you put there are more GDB scripts, not configuration files.
> So it is probably OK for them but I just would not call this feature
> system-gdbinit, I find it more contrib-scripts.
>
> system-gdbinit is /etc/gdbinit (Debian has some similar file there)
> which seems unrelated to this mail thread feature to me.
We added the --with-system-gdbinit configure option in order to
allow someone to build a GDB that would use another file as
the system-wide gdbinit. The distinction you are trying to
establish between what constitutes or not a system-wide gdbinit
seems artificial and unnecessary.
Anyone is free to configure its GDB in the way they want, and
in particular, to use the --with-system-gdbinit option to provide
a script (yes, a script) that would automatically setup their
GDB in a way that's actually useful to them. Many times, I am
sure, they will setup their own script based on their own setup.
But for the platforms this patch mentions, the scripts I provide
would work out of the box, and thus would be a suitable system-
wide init file.
And again, there is no harm possible, since the decision to
use them is voluntary, as GDB needs to be configured with
the appropriate --with-system-gdbinit switch in order to
enable the script of their choice.
--
Joel
next prev parent reply other threads:[~2012-12-18 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 15:54 Joel Brobecker
2012-12-18 16:48 ` Jan Kratochvil
2012-12-18 16:57 ` Joel Brobecker
2012-12-18 17:39 ` Jan Kratochvil
2012-12-18 18:06 ` Joel Brobecker [this message]
2012-12-18 18:17 ` Jan Kratochvil
2013-05-10 12:35 ` Joel Brobecker
2013-05-21 6:55 ` Checked in: " Joel Brobecker
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=20121218180555.GL3273@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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