From: Simon Marchi <simark@simark.ca>
To: Keith Seitz <keiths@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Pass INTERNAL_GDBFLAGS when executing GDB
Date: Wed, 17 Jun 2020 14:37:53 -0400 [thread overview]
Message-ID: <2a951e27-be83-6c7d-40c9-08091db484d6@simark.ca> (raw)
In-Reply-To: <20200617155617.3266224-1-keiths@redhat.com>
On 2020-06-17 11:56 a.m., Keith Seitz via Gdb-patches wrote:
> gdb.debuginfod/fetch_src_and_symbols.exp attempts to ascertain
> whether GDB was built with debuginfod support by executing
> "$GDB --configuration".
>
> That seems harmless enough. However, if GDB is not already installed
> on the host, the command will fail:
>
> $ ./gdb --config
> Exception caught while booting Guile.
> Error in function "open-file":
> No such file or directory: "/usr/share/gdb/guile/gdb/boot.scm"
> ./gdb: warning: Could not complete Guile gdb module initialization from:
> /usr/share/gdb/guile/gdb/boot.scm.
> Limited Guile support is available.
> Suggest passing --data-directory=/path/to/gdb/data-directory.
> Python Exception <class 'ModuleNotFoundError'> No module named 'gdb':
> ./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.
> This GDB was configured as follows:
> configure --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu
> [abbreviated output]
>
> The problem here is, of course, that while running in the test suite,
> we must pass INTERNAL_GDBFLAGS in order to pick up the --data-directory
> option.
>
> gdb/testsuite/ChangeLog
> 2020-06-17 Keith Seitz <keiths@redhat.com>
>
> * gdb.deuginfod/fetch_src_and_symbols.exp: Pass INTERNAL_GDBFLAGS
> when executing "gdb --configuration".
Watch out the typoe in "debuginfod".
Simon
next prev parent reply other threads:[~2020-06-17 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 15:56 Keith Seitz
2020-06-17 16:40 ` Tom Tromey
2020-06-17 17:45 ` Keith Seitz
2020-06-17 18:37 ` Simon Marchi [this message]
2020-06-17 22:09 ` Keith Seitz
2020-06-18 2:24 ` Simon Marchi
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=2a951e27-be83-6c7d-40c9-08091db484d6@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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).