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] New: gdb.fortran/mixed-lang-stack.exp: error reading variable in backtrace
Date: Fri, 14 Aug 2020 11:48:36 +0000	[thread overview]
Message-ID: <bug-26390-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=26390

            Bug ID: 26390
           Summary: gdb.fortran/mixed-lang-stack.exp: error reading
                    variable in backtrace
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: symtab
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

[ I'm using gcc-8 for this PR, the test-case seems to have been implemented
with gcc-8 and later abi in mind, see PR26362 comment 22.  FWIW, same behaviour
with gcc-11. ]

While looking into PR26362 I noticed this in the backtrace on a successful test
run on x86_64:
...
#7  0x000000000040114f in mixed_func_1b (a=1, b=2, c=3, d=(4,5), e=<error
reading variable: value requires 140737488341744 bytes, which is more than
max-value-size>, g=..., _e=6) at mixed-lang-stack.f90:87^M
...

Grepping for it, it reproduces with all 4 language setttings:
...
$ grep e= gdb.log | sed 's/.* e=/e=/;s/g=.*//'
e=<error reading variable: value requires 140737488341744 bytes, which is more
than max-value-size>, 
e=..., 
e=..., 
e=<error reading variable: value requires 140737488341744 bytes, which is more
than max-value-size>, 
e=..., 
e=..., 
e=<error reading variable: value requires 140737488341744 bytes, which is more
than max-value-size>, 
e=..., 
e=..., 
e=<error reading variable: value requires 140737488341744 bytes, which is more
than max-value-size>, 
e=..., 
e=..., 
...

The e='...' are due to printing of e when it's the current frame (resulting
from commands "up/down" or "info frame"), and with this:
...
diff --git a/gdb/testsuite/gdb.fortran/mixed-lang-stack.exp
b/gdb/testsuite/gdb.fortran/mix
ed-lang-stack.exp
index 793318626d..4047b548f9 100644
--- a/gdb/testsuite/gdb.fortran/mixed-lang-stack.exp
+++ b/gdb/testsuite/gdb.fortran/mixed-lang-stack.exp
@@ -50,6 +50,7 @@ proc run_tests { lang } {

        gdb_breakpoint "breakpt"
        gdb_continue_to_breakpoint "breakpt"
+       gdb_test_no_output "set print frame-arguments all"

        if { $lang == "c" || $lang == "c++" } {
            gdb_test "set language c" \
...
we have instead:
...
$ grep e= gdb.log | sed 's/.* e=/e=/;s/g=.*//'
e=<error reading variable: value requires 140737488341744 bytes, which is more
than max-value-size>, 
e='abcdef', 
e='abcdef', 
e=<error reading variable: value requires 140737488341744 bytes, which is more
than max-value-size>, 
e='abcdef', 
e='abcdef', 
e=<error reading variable: value requires 140737488341744 bytes, which is more
than max-value-size>, 
e="abcdef", 
e="abcdef", 
e=<error reading variable: value requires 140737488341744 bytes, which is more
than max-value-size>, 
e="abcdef", 
e="abcdef", 
...

So, this seems to be backtrace-specific.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-08-14 11:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-14 11:48 vries at gcc dot gnu.org [this message]
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
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@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).