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/29179] New: [cc-with-gdb-index] FAIL: gdb.ada/O2_float_param.exp: scenario=all: gdb_breakpoint: set breakpoint at increment
Date: Wed, 25 May 2022 14:35:03 +0000	[thread overview]
Message-ID: <bug-29179-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29179
           Summary: [cc-with-gdb-index] FAIL: gdb.ada/O2_float_param.exp:
                    scenario=all: gdb_breakpoint: set breakpoint at
                    increment
           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: ---

When running the testsuite with target board cc-with-gdb-index I see a lot of
FAILs.

First one:
...
(gdb) break increment^M
Function "increment" not defined.^M
Make breakpoint pending on future shared library load? (y or [n]) n^M
(gdb) FAIL: gdb.ada/O2_float_param.exp: scenario=all: gdb_breakpoint: set
breakpoint at increment
...

This passes with gdb 12 branch, so this is a regression.

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

             reply	other threads:[~2022-05-25 14:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25 14:35 vries at gcc dot gnu.org [this message]
2022-05-26  7:35 ` [Bug symtab/29179] " vries at gcc dot gnu.org
2022-07-08 11:39 ` vries at gcc dot gnu.org
2022-09-21 19:32 ` tromey at sourceware dot org
2022-09-21 20:03 ` tromey at sourceware dot org
2022-09-21 20:24 ` tromey at sourceware dot org
2022-09-22 20:28 ` tromey at sourceware dot org
2022-10-17 16:11 ` cvs-commit at gcc dot gnu.org
2022-10-17 16:11 ` cvs-commit at gcc dot gnu.org
2022-10-17 16:11 ` tromey at sourceware dot 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-29179-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).