From: Joel Brobecker <brobecker@adacore.com>
To: Reuben Thomas via Gdb <gdb@sourceware.org>
Subject: Re: Adding Python files to be autoloaded for a particular architecture
Date: Fri, 17 Jul 2020 14:42:10 -0700 [thread overview]
Message-ID: <20200717214210.GU5016@adacore.com> (raw)
In-Reply-To: <CAOnWdojq2PBG-VZ=2EONDqNs8zPzdj8Ju=tBkGo5ND6QjmLsRQ@mail.gmail.com>
> This seems to be a suitable candidate for SYSTEM_GDBINIT_FILES. But if I
> simply add a file to `SYSTEM_GDBINIT_FILES` in
> `gdb/data-directory/Makefile.in`, and then configure with
>
> --with-system-gdbinit-dir=$pkgdatadir/system-gdbinit
You can try with --with-system-gdbinit=xxx instead.
> then all of the files are installed (there are already two existing files,
> `elinos.py` and `wrs-linux.py`) and loaded when gdb starts up. This causes
> errors, as `wrs-linux.py` in particular expects to find an environment
> variable which I have not set.
We can probably delete these two files, if no one else finds them useful
anymore. But I don't think you really want to use GDB's system-gdbinit
as a system-gdbinit-dir; generally speaking, my understand of the
directory provided in the GDB sources is that it's a collection of
files that are not necessarily meant to always be relevant.
--
Joel
next prev parent reply other threads:[~2020-07-17 21:42 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 [this message]
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
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=20200717214210.GU5016@adacore.com \
--to=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).