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 16:57:00 -0000 [thread overview]
Message-ID: <20121218165706.GK3273@adacore.com> (raw)
In-Reply-To: <20121218164741.GB23234@host2.jankratochvil.net>
> But I do not see this problem solved in your patch, how do you execute
> those files?
My patch does not address the problem you point out. This is an
orthogonal issue, IMO.
> Besides that I find such files more as configuration files where read-only
> $(GDB_DATADIR) is not a suitable location.
Can you explain why not? As I said, for some systems, it works
universally, so sharing them across users in the read-only GDB_DATADIR
seems fine to me.
--
Joel
next prev parent reply other threads:[~2012-12-18 16:57 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 [this message]
2012-12-18 17:39 ` Jan Kratochvil
2012-12-18 18:06 ` Joel Brobecker
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=20121218165706.GK3273@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