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/30539] New: [gdb/testsuite] FAIL: gdb.ada/out_of_line_in_inlined.exp: scenario=all: run to foo_o224_021.child1.child2
Date: Mon, 12 Jun 2023 07:27:45 +0000 [thread overview]
Message-ID: <bug-30539-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30539
Bug ID: 30539
Summary: [gdb/testsuite] FAIL:
gdb.ada/out_of_line_in_inlined.exp: scenario=all: run
to foo_o224_021.child1.child2
Product: gdb
Version: 13.1
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With a gdb 13.1 based package on openSUSE Factory i586, I run into:
...
(gdb) run ^M
Starting program:
/home/abuild/rpmbuild/BUILD/gdb-13.2/build-i586-suse-linux/gdb/testsuite.unix.-m32.-fno-PIE.-no-pie/outputs/gdb.ada/out_of_line_in_inlined/foo_o224_021-all
^M
[Thread debugging using libthread_db enabled]^M
Using host libthread_db library "/lib/libthread_db.so.1".^M
^M
Breakpoint 1.1, foo_o224_021.child1.child2 (s=...) at
/home/abuild/rpmbuild/BUILD/gdb-13.2/gdb/testsuite/gdb.ada/out_of_line_in_inlined/foo_o224_021.adb:26^M
26 for C of S loop^M
(gdb) FAIL: gdb.ada/out_of_line_in_inlined.exp: scenario=all: run to
foo_o224_021.child1.child2
...
The test-case checks for "Breakpoint $decimal", should probably use
bkptno_num_re.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-06-12 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 7:27 vries at gcc dot gnu.org [this message]
2023-06-12 9:14 ` [Bug testsuite/30539] " cvs-commit at gcc dot gnu.org
2023-06-12 9:15 ` 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-30539-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).