From: "Ludovic Courtès" <ludo@gnu.org>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 70393@debbugs.gnu.org, Tanguy Le Carrour <tanguy@bioneland.org>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
Christopher Baines <mail@cbaines.net>, jgart <jgart@dismail.de>,
Marius Bakke <marius@gnu.org>,
Sharlatan Hellseher <sharlatanus@gmail.com>
Subject: [bug#70393] [PATCH] gnu: python-pydevd: Use gdb/pinned.
Date: Wed, 01 May 2024 11:53:10 +0200 [thread overview]
Message-ID: <87sez17ta1.fsf@gnu.org> (raw)
In-Reply-To: <ZipyIWiBNAJdpuI9@noor.fritz.box> (Lars-Dominik Braun's message of "Thu, 25 Apr 2024 17:09:21 +0200")
Hi,
Lars-Dominik Braun <lars@6xq.net> skribis:
>> > If PyDev uses GDB, then it’ll be stuck with an older version of GDB?
>> > Maybe that’s OK? (I know nothing about PyDev and how it uses GDB so I
>> > can’t really judge whether it’s OK.)
>>
>> I don't really know either, but at least this will allow updating gdb
>> without rebuilding a bunch of Python things.
>
> I don’t see anything that would prevent pydevd running on a pinned/older
> GDB version. We might want to verify when we update python-pydevd, but
> right now it just attaches to the process and injects a shared object
> – that’s all. So, LGTM.
OK, thanks for checking. Go for it, Chris!
Ludo’.
prev parent reply other threads:[~2024-05-01 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 8:25 [bug#70393] [PATCH] gnu: python-pydevd: Use gdb/pinned Christopher Baines
2024-04-15 16:27 ` Ludovic Courtès
2024-04-17 13:43 ` Christopher Baines
2024-04-25 15:09 ` Lars-Dominik Braun
2024-05-01 9:53 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sez17ta1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=70393@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=mail@cbaines.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).