public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/30908] [gdb/ada, gcc 13] FAIL: gdb.ada/str_binop_equal.exp: print my_str = "ABCD"
Date: Mon, 02 Oct 2023 17:48:29 +0000	[thread overview]
Message-ID: <bug-30908-4717-SdmzZvOvJU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30908-4717@http.sourceware.org/bugzilla/>

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

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=89238cfdbaadede9817f0848202f1d34f9885d94

commit 89238cfdbaadede9817f0848202f1d34f9885d94
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Oct 2 19:48:21 2023 +0200

    [gdb/testsuite] Add KFAIL for PR ada/30908

    With gcc 13.2.1, I run into a cluster of fails:
    ...
    FAIL: gdb.ada/str_binop_equal.exp: print my_str = "ABCD"
    FAIL: gdb.ada/widewide.exp: print my_wws = " helo"
    FAIL: gdb.ada/widewide.exp: print my_ws = "wide"
    ...

    The problem is that the debug info contains information about function
    ada.strings.maps."=", and gdb uses it to implement the comparison.
    The function is supposed to compare two char sets, not strings, so gdb
    shouldn't use it.  This is PR ada/30908.

    I don't see the same problem with gcc 7.5.0, because the exec doesn't
contain
    the debug info for the function, because the corresponding object is not
    linked in.  Adter adding "with Ada.Strings.Maps; use Ada.Strings.Maps;" to
    gdb.ada/widewide/foo.adb I run into the same problem with gcc 7.5.0.

    Add KFAILs for the PR.

    Tested on x86_64-linux:
    - openSUSE Leap 15.4 (using gcc 7.5.0), and
    - openSUSE Tumbleweed (using gcc 13.2.1).

    Approved-By: Tom Tromey <tom@tromey.com>

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

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

  parent reply	other threads:[~2023-10-02 17:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 15:11 [Bug ada/30908] New: " vries at gcc dot gnu.org
2023-09-26 15:37 ` [Bug ada/30908] " tromey at sourceware dot org
2023-09-26 17:14 ` vries at gcc dot gnu.org
2023-09-26 23:31 ` vries at gcc dot gnu.org
2023-09-27  6:58 ` vries at gcc dot gnu.org
2023-10-01 13:26 ` vries at gcc dot gnu.org
2023-10-02 17:48 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-26 18:38 ` tromey at sourceware dot org
2024-02-27 11:14 ` vries at gcc dot gnu.org
2024-02-27 11:23 ` vries at gcc dot gnu.org
2024-02-27 15:21 ` cvs-commit 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-30908-4717-SdmzZvOvJU@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).