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 gdb/29920] New: [gdb] FAIL: gdb.cp/step-and-next-inline.exp: no_header: next step 1
Date: Tue, 20 Dec 2022 08:58:26 +0000 [thread overview]
Message-ID: <bug-29920-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29920
Bug ID: 29920
Summary: [gdb] FAIL: gdb.cp/step-and-next-inline.exp:
no_header: next step 1
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On ubuntu 22.04.1 x86_64 with gcc 11.3.0, I run into:
...
(gdb) PASS: gdb.cp/step-and-next-inline.exp: no_header: step into get_alias_set
bt^M
#0 get_alias_set (t=t@entry=0x555555558018 <xx>) at
/home/vries/gdb/src/gdb/testsuite/gdb.cp/step-and-next-inline.cc:50^M
#1 0x0000555555555084 in main () at
/home/vries/gdb/src/gdb/testsuite/gdb.cp/step-and-next-inline.cc:64^M
((gdb) PASS: gdb.cp/step-and-next-inline.exp: no_header: not in inline 1
next^M
51 if (t != NULL^M
(gdb) FAIL: gdb.cp/step-and-next-inline.exp: no_header: next step 1
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-12-20 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 8:58 vries at gcc dot gnu.org [this message]
2022-12-20 9:14 ` [Bug gdb/29920] " vries at gcc dot gnu.org
2022-12-20 9:48 ` [Bug testsuite/29920] [gdb/testsuite] " vries at gcc dot gnu.org
2022-12-21 8:07 ` vries at gcc dot gnu.org
2022-12-23 8:15 ` vries at gcc dot gnu.org
2022-12-30 13:00 ` cvs-commit at gcc dot gnu.org
2022-12-30 13:02 ` 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-29920-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).