From: Carl Love <cel@us.ibm.com>
To: Andrew Burgess <aburgess@redhat.com>, Tom Tromey <tom@tromey.com>,
Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Subject: RE: [PATCH 2/2] gdb/python: improve formatting of help text for user defined commands
Date: Fri, 03 Jun 2022 11:05:23 -0700 [thread overview]
Message-ID: <5ad1534d98e1c6132722d663180a97ebcc2075df.camel@us.ibm.com> (raw)
In-Reply-To: <73f20772cf68f5f966d82ff005b430a34f6ba1a3.camel@us.ibm.com>
Andrew:
On Tue, 2022-05-31 at 16:10 -0700, Carl Love wrote:
> > I am seeing failures with the new test gdb/testsuite/gdb.python/py-
> > doc-
> > reformat.exp on X86-64 and Power. The errors show up in the full
>
> My bad, I forgot to mention that the failure is on Power 7, RHEL
> 7.9.
> I was digging a bit more on the "undefined source" error messages
> below
> about the source . I noticed that the python version was 2.7.5. I
> checked the test on a Power 10, RHEL 9.0, box and found that it
> worked.
> The power 10 box has python version 3.9.10. I am using the bash
> shell
> on both systems to run the gdb tests. Not sure if a newer version of
> python is needed for the source command. So far I haven't found
> anything about the source command being version dependent.
>
> The intel box is Ubuntu 22.04, does not have python but rather
> python3
> version 3.10.4. Given that I was able to get it to run on a Power
> 10
> box but not a Power 7 box would indicate it is some sort of a system
> setup issue? Any thoughts on what it might be? I will keep digging.
I found the root cause of the failures. The test needs python3 to run
correctly. The machines where I was seeing the failures were still on
distros using python 2. Specifically, RHEL 7.8 uses python 2 by
default. Installing python 3 and changing the soft link
/usr/bin/python to point to python3 fixes the issue.
Carl Love
next prev parent reply other threads:[~2022-06-03 18:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 10:51 [PATCH 0/2] Improve help test for commands defined in Python Andrew Burgess
2022-05-17 10:51 ` [PATCH 1/2] gdb: use gdb::unique_xmalloc_ptr<char> for docs in cmdpy_init Andrew Burgess
2022-05-26 17:43 ` Tom Tromey
2022-05-28 10:10 ` Andrew Burgess
2022-05-17 10:51 ` [PATCH 2/2] gdb/python: improve formatting of help text for user defined commands Andrew Burgess
2022-05-17 12:19 ` Eli Zaretskii
2022-05-17 22:41 ` Lancelot SIX
2022-05-18 10:19 ` Andrew Burgess
2022-05-18 12:09 ` Eli Zaretskii
2022-05-26 17:46 ` Tom Tromey
2022-05-28 10:11 ` Andrew Burgess
2022-05-31 21:54 ` Carl Love
2022-05-31 23:10 ` Carl Love
2022-06-03 18:05 ` Carl Love [this message]
2022-06-06 11:40 ` [PUSHED] gdb/testsuite: add missing skip_python_tests call in py-doc-reformat.exp Andrew Burgess
2022-06-07 16:08 ` Carl Love
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=5ad1534d98e1c6132722d663180a97ebcc2075df.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).