public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/26390] gdb.fortran/mixed-lang-stack.exp: error reading variable in backtrace
Date: Fri, 14 Aug 2020 15:38:43 +0000 [thread overview]
Message-ID: <bug-26390-4717-W5wMO5hYOZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26390-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26390
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brobecke at sourceware dot org
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #5)
> Tentative patch, code copied from print_frame_local_vars:
> ...
> diff --git a/gdb/stack.c b/gdb/stack.c
> index 265e764dc2..b63f109031 100644
> --- a/gdb/stack.c
> +++ b/gdb/stack.c
> @@ -743,6 +743,12 @@ print_frame_args (const frame_print_options &fp_opts,
> bool print_args
> = (print_names
> && fp_opts.print_frame_arguments != print_frame_arguments_none);
> +
> + /* Temporarily change the selected frame to the given FRAME.
> + This allows routines that rely on the selected frame instead
> + of being given a frame as parameter to use the correct frame. */
> + scoped_restore_selected_frame restore_selected_frame;
> + select_frame (frame);
>
> if (func)
> {
> ...
Yep, the problem sounds rather similar to what is described here:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=16c3b12f199a7ec99a0b51bd83b66942547bba87
.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-14 15:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 11:48 [Bug symtab/26390] New: " vries at gcc dot gnu.org
2020-08-14 12:03 ` [Bug symtab/26390] " vries at gcc dot gnu.org
2020-08-14 12:49 ` vries at gcc dot gnu.org
2020-08-14 14:52 ` vries at gcc dot gnu.org
2020-08-14 15:12 ` vries at gcc dot gnu.org
2020-08-14 15:15 ` vries at gcc dot gnu.org
2020-08-14 15:38 ` vries at gcc dot gnu.org [this message]
2020-08-14 15:39 ` vries at gcc dot gnu.org
2020-08-15 5:48 ` [Bug backtrace/26390] " vries at gcc dot gnu.org
2020-08-15 5:55 ` vries at gcc dot gnu.org
2020-08-15 8:19 ` cvs-commit at gcc dot gnu.org
2020-08-15 8:27 ` vries at gcc dot gnu.org
2020-08-15 8:28 ` vries at gcc dot gnu.org
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=bug-26390-4717-W5wMO5hYOZ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).