From: CtrlC-Root <CtrlC-Root@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cross-arm-none-eabi-gdb appears to be missing some Python modules
Date: Sun, 09 Jul 2023 17:29:29 +0200 [thread overview]
Message-ID: <20230709152929.DK_tNzE7fycrU9CpTPf3A27x4qGjvwM6rWfC3isgBA0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44594@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
New comment by CtrlC-Root on void-packages repository
https://github.com/void-linux/void-packages/issues/44594#issuecomment-1627748317
Comment:
I have run into this as well and here's my understanding of the situation. If the `cross-arm-none-eabi-gdb` and `gdb-common` packages have matching versions then the former will use the Python libraries shipped with the latter at `/usr/share/gdb/python/`. However at the moment on Void Linux the former is 12.X and the latter is 13.X which apparently are incompatible hence the errors above. This prevents you from using most of the Python-based GDB tools with the `cross-arm-none-eabi-gdb` package (ex. [gef](https://github.com/hugsy/gef)).
I'm not sure the best way to fix this but off the top of my head:
* Build the GDB 12 Python libraries, install them at a separate path than the default, and point GDB to them explicitly using configuration settings.
* Update `cross-arm-none-eabi-gdb` to the same major version as `gdb-common` and `gdb`. Now they can both use the same Python libraries.
next prev parent reply other threads:[~2023-07-09 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 17:46 [ISSUE] " camthesaxman
2023-06-26 5:11 ` CabrioletDiskette
2023-06-26 5:12 ` CabrioletDiskette
2023-06-26 5:21 ` CabrioletDiskette
2023-06-26 5:22 ` CabrioletDiskette
2023-06-26 5:24 ` CabrioletDiskette
2023-07-09 15:29 ` CtrlC-Root
2023-07-09 15:29 ` CtrlC-Root [this message]
2023-07-09 15:30 ` CtrlC-Root
2023-07-10 9:19 ` [ISSUE] [CLOSED] " classabbyamp
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=20230709152929.DK_tNzE7fycrU9CpTPf3A27x4qGjvwM6rWfC3isgBA0@z \
--to=ctrlc-root@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).