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/30548] New: [gdb, ppc64le, s390x] FAIL: gdb.base/inline-frame-cycle-unwind.exp: cycle at level 5: backtrace when the unwind is broken at frame 5
Date: Tue, 13 Jun 2023 14:19:35 +0000 [thread overview]
Message-ID: <bug-30548-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30548
Bug ID: 30548
Summary: [gdb, ppc64le, s390x] FAIL:
gdb.base/inline-frame-cycle-unwind.exp: cycle at level
5: backtrace when the unwind is broken at frame 5
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: ---
I'm running into these FAILs with ppc64le and s390x:
...
FAIL: gdb.base/inline-frame-cycle-unwind.exp: cycle at level 5: backtrace when
the unwind is broken at frame 5
FAIL: gdb.base/inline-frame-cycle-unwind.exp: cycle at level 3: backtrace when
the unwind is broken at frame 3
FAIL: gdb.base/inline-frame-cycle-unwind.exp: cycle at level 1: backtrace when
the unwind is broken at frame 1
...
First in more detail:
...
(gdb) PASS: gdb.base/inline-frame-cycle-unwind.exp: cycle at level 5: maint
flush register-cache
bt^M
#0 inline_func () at
/home/vries/gdb/src/gdb/testsuite/gdb.base/inline-frame-cycle-unwind.c:49^M
#1 normal_func () at
/home/vries/gdb/src/gdb/testsuite/gdb.base/inline-frame-cycle-unwind.c:32^M
#2 0x0000000010000734 in inline_func () at
/home/vries/gdb/src/gdb/testsuite/gdb.base/inline-frame-cycle-unwind.c:45^M
#3 normal_func () at
/home/vries/gdb/src/gdb/testsuite/gdb.base/inline-frame-cycle-unwind.c:32^M
register has not been saved in frame^M
(gdb) FAIL: gdb.base/inline-frame-cycle-unwind.exp: cycle at level 5: backtrace
when the unwind is broken at frame 5
...
Fails quite consistently, from SLE-12 to Tumbleweed:
...
$ find tmp-qa-remote/ -name "*.sum" | xargs grep -c "FAIL:
gdb.base/inline-frame-cycle-unwind.exp" | grep -v :0
tmp-qa-remote/binaries-testsuite.SLE-15.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.-fno-PIE.-no-pie.sum:3
tmp-qa-remote/binaries-testsuite.SLE-15.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Leap_15.4.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.-fno-PIE.-no-pie.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Leap_15.4.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Factory_PPC.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Factory_PPC.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.-fno-PIE.-no-pie.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Factory_ARM.armv7l/gdb-testresults/gdb-armv7hl-suse-linux.-fno-PIE.-no-pie.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Factory_ARM.armv7l/gdb-testresults/gdb-armv7hl-suse-linux.sum:3
tmp-qa-remote/binaries-testsuite.SLE-15.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.sum:3
tmp-qa-remote/binaries-testsuite.SLE-15.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.-fno-PIE.-no-pie.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Factory_zSystems.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.-fno-PIE.-no-pie.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Factory_zSystems.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Leap_15.3.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Leap_15.3.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.-fno-PIE.-no-pie.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Leap_15.4.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Leap_15.4.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.-fno-PIE.-no-pie.sum:3
tmp-qa-remote/binaries-testsuite.SLE-12.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.-fPIE.-pie.sum:3
tmp-qa-remote/binaries-testsuite.SLE-12.ppc64le/gdb-testresults/gdb-ppc64le-suse-linux-m64.sum:3
tmp-qa-remote/binaries-testsuite.SLE-12.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.sum:3
tmp-qa-remote/binaries-testsuite.SLE-12.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.-fPIE.-pie.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Leap_15.3.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.-fno-PIE.-no-pie.sum:3
tmp-qa-remote/binaries-testsuite.openSUSE_Leap_15.3.s390x/gdb-testresults/gdb-s390x-suse-linux-m64.sum:3
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-06-13 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:19 vries at gcc dot gnu.org [this message]
2024-02-14 9:23 ` [Bug gdb/30548] " vries at gcc dot gnu.org
2024-05-08 8:37 ` vries at gcc dot gnu.org
2024-05-08 12: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-30548-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).