public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Christian Biesinger <cbiesinger@google.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	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:21:58 +0100	[thread overview]
Message-ID: <CAOnWdoj=zFxPBLpCMT_w1obmRJCuQ8yZNjTvGzYtpah5r0mntg@mail.gmail.com> (raw)
In-Reply-To: <CAPTJ0XEN9GVZe8UD5YWFbUEpm_EtYX5L6iC=XfJUEYTewysYUQ@mail.gmail.com>

On Fri, 17 Jul 2020 at 23:10, Christian Biesinger <cbiesinger@google.com>
wrote:

>
> You could certainly add new rules modeled after the system-gdbinit
> ones in gdb/data-directory/Makefile.in?
>

Thanks for your suggestion! Sorry if I'm failing to understand something
obvious, but what exactly do you mean by "new rules modeled after the
system-gdbinit ones"? In particular, it's not obvious to me how such a rule
would cause the file(s) I add to be automatically loaded on startup,
without also adding support for some other directory to GDB itself.

-- 
https://rrt.sc3d.org

  reply	other threads:[~2020-07-17 22:22 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 [this message]
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

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='CAOnWdoj=zFxPBLpCMT_w1obmRJCuQ8yZNjTvGzYtpah5r0mntg@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=brobecker@adacore.com \
    --cc=cbiesinger@google.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).