From: Reuben Thomas <rrt@sc3d.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: Adding Python files to be autoloaded for a particular architecture
Date: Fri, 17 Jul 2020 23:18:55 +0100 [thread overview]
Message-ID: <CAOnWdog7yQqT3bR4BF2dQOOnJ=vhaMEz5u3mzRaJAbcPgVrdcQ@mail.gmail.com> (raw)
In-Reply-To: <20200717221403.GV5016@adacore.com>
On Fri, 17 Jul 2020 at 23:14, Joel Brobecker <brobecker@adacore.com> wrote:
> > > You can try with --with-system-gdbinit=xxx instead.
> > >
> >
> > Thanks, but surely --with-system-gdbinit is designed for the system
> > administrator? For example, on Debian, the supplied gdb is configured
> with
> > --with-system-gdbinit=/etc/gdb/gdbinit. I don't want to conflict with
> this
> > usage.
>
> I don't think you can categorize the intended user of each option.
> They just do different things.
>
What I mean is that I cannot use --with-system-gdbinit for a solution that
I would eventually like to merge into gdb.
Thinking out loud (I do not know all the details off the top of my head),
> I see a couple of ways:
> - You use a subdirectory of system-gdbinit, and then configure GDB
> to use that subdirectory
> - You create one file that the sources all the other files you need,
> and then configure GDB to use that file as the system-gdbinit.
>
Again, both of these suggestions involve configuring GDB, so I don't see
how they can be suitable for code that can be merged into GDB.
Sorry if I'm failing to understand something here!
--
https://rrt.sc3d.org
prev parent reply other threads:[~2020-07-17 22:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 16:11 Reuben Thomas
2020-07-17 21:42 ` Joel Brobecker
2020-07-17 22:03 ` Reuben Thomas
2020-07-17 22:09 ` Christian Biesinger
2020-07-17 22:21 ` Reuben Thomas
2020-07-17 22:31 ` Christian Biesinger
2020-07-17 22:37 ` Reuben Thomas
2020-07-20 20:26 ` Christian Biesinger
2020-07-20 21:39 ` Reuben Thomas
2020-07-17 22:14 ` Joel Brobecker
2020-07-17 22:18 ` Reuben Thomas [this message]
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='CAOnWdog7yQqT3bR4BF2dQOOnJ=vhaMEz5u3mzRaJAbcPgVrdcQ@mail.gmail.com' \
--to=rrt@sc3d.org \
--cc=brobecker@adacore.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).