From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6E4C43857C52; Fri, 14 Aug 2020 11:48:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6E4C43857C52 From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: symtab X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2020 11:48:36 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26390 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 behav= iour 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=3D1, b=3D2, c=3D3, d=3D(4,5), e= =3D, g=3D..., _e=3D6) at mixed-lang-stack.f90:87^M ... Grepping for it, it reproduces with all 4 language setttings: ... $ grep e=3D gdb.log | sed 's/.* e=3D/e=3D/;s/g=3D.*//' e=3D,=20 e=3D...,=20 e=3D...,=20 e=3D,=20 e=3D...,=20 e=3D...,=20 e=3D,=20 e=3D...,=20 e=3D...,=20 e=3D,=20 e=3D...,=20 e=3D...,=20 ... The e=3D'...' are due to printing of e when it's the current frame (resulti= ng 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 =3D=3D "c" || $lang =3D=3D "c++" } { gdb_test "set language c" \ ... we have instead: ... $ grep e=3D gdb.log | sed 's/.* e=3D/e=3D/;s/g=3D.*//' e=3D,=20 e=3D'abcdef',=20 e=3D'abcdef',=20 e=3D,=20 e=3D'abcdef',=20 e=3D'abcdef',=20 e=3D,=20 e=3D"abcdef",=20 e=3D"abcdef",=20 e=3D,=20 e=3D"abcdef",=20 e=3D"abcdef",=20 ... So, this seems to be backtrace-specific. --=20 You are receiving this mail because: You are on the CC list for the bug.=