public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug record/29721] [gdb, record, aarch64] FAIL: gdb.reverse/solib-precsave.exp: reverse-next third shr1 Date: Wed, 26 Oct 2022 11:56:21 +0000 [thread overview] Message-ID: <bug-29721-4717-UyY6zvLI6Y@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29721-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29721 --- Comment #2 from B. Larsen <blarsen at redhat dot com> --- Running this test on Fedora 36 in aarch64, I only get 5 fails. Looking at the log: reverse-next^M 40 b[0] = 6; b[1] = 9; /* generic statement, end part two */^M (gdb) PASS: gdb.reverse/solib-precsave.exp: reverse-next generic reverse-step^M 40 b[0] = 6; b[1] = 9; /* generic statement, end part two */^M (gdb) FAIL: gdb.reverse/solib-precsave.exp: reverse-step into solib function one reverse-step^M 38 b[1] = shr2(17); /* middle part two */^M (gdb) FAIL: gdb.reverse/solib-precsave.exp: reverse-step within solib function one reverse-step^M shr2 (x=17) at /root/bld/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.reverse/shr2.c:23^M 23 }^M (gdb) FAIL: gdb.reverse/solib-precsave.exp: reverse-step back to main one reverse-step^M 22 return 2*x;^M (gdb) FAIL: gdb.reverse/solib-precsave.exp: reverse-step into solib function two reverse-step^M main () at /root/bld/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.reverse/solib-reverse.c:38^M 38 b[1] = shr2(17); /* middle part two */^M (gdb) FAIL: gdb.reverse/solib-precsave.exp: reverse-step within solib function two It seems that aarch64 is also experiencing https://sourceware.org/bugzilla/show_bug.cgi?id=28426 now, and x86 stopped experiencing it. While I agree that this should be fixed, I'm not sure 1f3e37e057e876b37db49dbd8ed5ca22c33f6772 is the actual culprit. I'll add this to my backlog, but it is pretty low priority, since testing in aarch64 is cumbersome for me, unfortunately. Also, if you are still seeing the failures with third, second and first shr1 with the cureent trunk, please post the relevant log here :-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-26 11:56 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-25 13:30 [Bug record/29721] New: " vries at gcc dot gnu.org 2022-10-25 16:20 ` [Bug record/29721] " vries at gcc dot gnu.org 2022-10-26 11:56 ` blarsen at redhat dot com [this message] 2022-10-26 14:16 ` vries at gcc dot gnu.org 2022-10-26 14:36 ` blarsen at redhat dot com 2022-10-26 14:43 ` vries at gcc dot gnu.org 2022-10-26 14:47 ` vries at gcc dot gnu.org 2022-10-27 20:15 ` luis.machado at arm dot com 2022-11-02 14:05 ` vries at gcc dot gnu.org 2022-11-02 15:42 ` blarsen at redhat dot com 2022-11-08 16:08 ` blarsen at redhat dot com 2022-11-10 12:07 ` blarsen at redhat dot com 2022-11-10 12:40 ` luis.machado at arm dot com 2022-11-10 14:18 ` vries at gcc dot gnu.org 2022-11-10 14:20 ` vries at gcc dot gnu.org 2022-12-13 14:57 ` blarsen at redhat dot com 2023-01-16 10:43 ` vries at gcc dot gnu.org 2023-01-16 15:58 ` vries at gcc dot gnu.org 2023-01-16 16:40 ` vries at gcc dot gnu.org 2023-01-16 18:59 ` luis.machado at arm dot com 2023-01-16 19:39 ` vries at gcc dot gnu.org 2023-01-16 19:53 ` luis.machado at arm dot com 2023-01-16 19:57 ` vries at gcc dot gnu.org 2023-01-17 16:47 ` vries at gcc dot gnu.org 2023-01-19 13:42 ` vries at gcc dot gnu.org 2023-01-19 13:46 ` vries at gcc dot gnu.org 2023-01-19 13:47 ` vries at gcc dot gnu.org 2023-01-19 13:56 ` luis.machado at arm dot com 2023-01-19 14:00 ` vries at gcc dot gnu.org 2023-01-19 14:14 ` vries at gcc dot gnu.org 2023-01-19 14:28 ` blarsen at redhat dot com 2023-01-19 17:30 ` vries at gcc dot gnu.org 2023-01-20 8:57 ` blarsen at redhat dot com
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-29721-4717-UyY6zvLI6Y@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: linkBe 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).