public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cel at us dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/30021] [gdb/tdep, powerpc64le] previous frame inner to this frame (corrupt stack?)
Date: Thu, 26 Jan 2023 16:12:51 +0000 [thread overview]
Message-ID: <bug-30021-4717-MEpvvrRaxI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30021-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30021
--- Comment #8 from Carl E Love <cel at us dot ibm.com> ---
I am seeing 11 new failures on our GDB build bot runs. They appear to be due
to the latest commit. There appear to be a couple of issues fixed.
158 failures
11 new failures
3 old failures fixed
+FAIL: gdb.base/gdb-sigterm.exp: pass=1: expect eof (GDB internal error)
+FAIL: gdb.base/unwind-on-each-insn.exp: bar: instruction 6: bt 2
+FAIL: gdb.base/unwind-on-each-insn.exp: bar: instruction 6: [string equal $fid
$::main_fid]
+FAIL: gdb.base/unwind-on-each-insn.exp: bar: instruction 6: up
+FAIL: gdb.base/unwind-on-each-insn.exp: bar: instruction 7: bt 2
+FAIL: gdb.base/unwind-on-each-insn.exp: bar: instruction 7: [string equal $fid
$::main_fid]
+FAIL: gdb.base/unwind-on-each-insn.exp: bar: instruction 7: up
+FAIL: gdb.base/unwind-on-each-insn.exp: bar: instruction 8: $fba_value ==
$::main_fba
+FAIL: gdb.base/unwind-on-each-insn.exp: bar: instruction 8: [string equal $fid
$::main_fid]
+FAIL: gdb.base/unwind-on-each-insn.exp: foo: instruction 7: $fba_value ==
$::main_fba
+FAIL: gdb.base/unwind-on-each-insn.exp: foo: instruction 7: [string equal $fid
$::main_fid]
-FAIL: gdb.base/gdb-sigterm.exp: pass=0: expect eof (GDB internal error)
-FAIL: gdb.base/unwind-on-each-insn.exp: instruction 6: $fba_value == $main_fba
-FAIL: gdb.base/unwind-on-each-insn.exp: instruction 6: [string equal $fid
$main_fid]
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-26 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 16:01 [Bug tdep/30021] New: " vries at gcc dot gnu.org
2023-01-19 11:14 ` [Bug tdep/30021] " vries at gcc dot gnu.org
2023-01-23 15:33 ` vries at gcc dot gnu.org
2023-01-23 15:38 ` vries at gcc dot gnu.org
2023-01-24 0:14 ` vries at gcc dot gnu.org
2023-01-24 10:46 ` vries at gcc dot gnu.org
2023-01-24 11:46 ` vries at gcc dot gnu.org
2023-01-25 12:27 ` cvs-commit at gcc dot gnu.org
2023-01-26 16:12 ` cel at us dot ibm.com [this message]
2023-01-26 16:14 ` cel at us dot ibm.com
2023-01-26 16:16 ` 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-30021-4717-MEpvvrRaxI@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).