Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] cross-arm-none-eabi-gdb appears to be missing some Python modules
Date: Mon, 10 Jul 2023 11:19:36 +0200	[thread overview]
Message-ID: <20230710091936.uUxw7sVWm9rfjaGn1NCeGQQlX6EYPxRIgwS4JctO-QU@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: 2995 bytes --]

Closed issue by camthesaxman on void-packages repository

https://github.com/void-linux/void-packages/issues/44594

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.25_1 x86_64 GenuineIntel uptodate hold rrrmFFFFFF

### Package(s) Affected

cross-arm-none-eabi-gdb-12.1_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

The `arm-none-eabi-gdb` command should work correctly without warnings.

### Actual behaviour

arm-none-eabi-gdb throws numerous warnings about Python modules not being found. Most debugging features still work, though there are annoying warnings with every command. The native x86-64 gdb does not exhibit this behavior, but the arm gdb does. Sample output from debugging an ARM kernel in qemu:
```
Python Exception <class 'ModuleNotFoundError'>: No module named '_gdbevents'
arm-none-eabi-gdb: warning:
Could not load the Python gdb module from `/usr/share/gdb/python'.
Limited Python support is available from the _gdb module.
Suggest passing --data-directory=/path/to/gdb/data-directory.
GNU gdb (GDB) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kernel.elf...
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
Python Exception <class 'NameError'>: Installation error: gdb._execute_unwinders function is missing
0x00008000 in bootstrap ()
(gdb) stepi
Python Exception <class 'NameError'>: Installation error: gdb._execute_unwinders function is missing
Python Exception <class 'NameError'>: Installation error: gdb._execute_unwinders function is missing
0x00008004 in bootstrap ()
(gdb)
Python Exception <class 'NameError'>: Installation error: gdb._execute_unwinders function is missing
Python Exception <class 'NameError'>: Installation error: gdb._execute_unwinders function is missing
0x00008008 in bootstrap ()
(gdb) q
A debugging session is active.

        Inferior 1 [process 1] will be detached.

Quit anyway? (y or n) y
Detaching from program: /home/void/rpi-baremetal/kernel.elf, process 1
Ending remote debugging.
```

### Steps to reproduce

1. Install cross-arm-none-eabi-gdb.
2. Run arm-none-eabi-gdb.
3. Run some commands in gdb and get spammed with Python errors.

      parent reply	other threads:[~2023-07-10  9:19 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
2023-07-09 15:30 ` CtrlC-Root
2023-07-10  9:19 ` classabbyamp [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230710091936.uUxw7sVWm9rfjaGn1NCeGQQlX6EYPxRIgwS4JctO-QU@z \
    --to=classabbyamp@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).