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: Mon, 20 Jul 2020 22:39:14 +0100 [thread overview]
Message-ID: <CAOnWdogNeQZVXt9J=fzGMML91_Ryxip9KAG1xn9=598rtrDtbA@mail.gmail.com> (raw)
In-Reply-To: <CAPTJ0XHODXuFyrDJVR0jDqvOrV_9Frq2v2fSt82Hs+kYEJpTFw@mail.gmail.com>
On Mon, 20 Jul 2020 at 21:27, Christian Biesinger <cbiesinger@google.com>
wrote:
> I see. In that case, I see two options:
> - Put it in gdb/python/lib/gdb. That directory has so far only been
> used as an implementation detail for gdb's python API, but maybe
> maintainers will be OK with extending it in that way. That dir does
> get installed whenever python is enabled.
>
This feels like the wrong place, as after all what I'm implementing is not
an extension of the gdb package, but a use of it.
> - Or implement it in C++
>
It would be a shame to have to use another language.
However, there will certainly be some solution, and I guess I'll revisit
this once I have a contribution to submit to the maintainers.
Thanks very much for all your suggestions!
--
https://rrt.sc3d.org
next prev parent reply other threads:[~2020-07-20 21:39 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 [this message]
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='CAOnWdogNeQZVXt9J=fzGMML91_Ryxip9KAG1xn9=598rtrDtbA@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).