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 testsuite/31234] New: [gdb/testsuite, s390x] FAIL: gdb.fortran/mixed-lang-stack.exp: lang=auto: print obj
Date: Thu, 11 Jan 2024 15:00:08 +0000	[thread overview]
Message-ID: <bug-31234-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31234
           Summary: [gdb/testsuite, s390x] FAIL:
                    gdb.fortran/mixed-lang-stack.exp: lang=auto: print obj
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On s390x-linux, I ran into:
...
(gdb) PASS: gdb.fortran/mixed-lang-stack.exp: lang=auto: info frame in frame #2
print obj^M
value has been optimized out^M
(gdb) FAIL: gdb.fortran/mixed-lang-stack.exp: lang=auto: print obj
...

This is a regression since gdb 13, but it's due to a test-case patch:
...
commit a60ead5ded5f9fc548018637d4810cb5f313ad8c
Author: Nils-Christian Kempke <nils-christian.kempke@intel.com>
Date:   Tue May 31 16:43:45 2022 +0200

    gdb, testsuite, fortran: fix double free in mixed-lang-stack.exp
...

After reverting the patch, the FAIL disappears.

The difference is in the debug info.  In the passing case we have:
...
 <2><ce1>: Abbrev Number: 45 (DW_TAG_formal_parameter)
    <ce2>   DW_AT_name        : obj
    <ce6>   DW_AT_decl_file   : 1
    <ce7>   DW_AT_decl_line   : 75
    <ce8>   DW_AT_type        : <0xbd3>
    <cec>   DW_AT_location    : 4 byte block: 91 d8 7e 6        (DW_OP_fbreg:
-168; DW_OP_deref)
...
and in the failing case:
...
 <2><c3f>: Abbrev Number: 40 (DW_TAG_formal_parameter)
    <c40>   DW_AT_name        : obj
    <c44>   DW_AT_decl_file   : 1
    <c45>   DW_AT_decl_line   : 65
    <c46>   DW_AT_type        : <0xba2>
    <c4a>   DW_AT_location    : 2 byte block: 72 0      (DW_OP_breg2 (r2): 0)
...

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

             reply	other threads:[~2024-01-11 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 15:00 vries at gcc dot gnu.org [this message]
2024-01-11 15:01 ` [Bug testsuite/31234] " 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-31234-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).