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 tdep/31507] [gdb, aarch64] FAIL: gdb.arch/disp-step-insn-reloc.exp: can_relocate_adr_forward: relocated instruction
Date: Mon, 18 Mar 2024 17:49:30 +0000 [thread overview]
Message-ID: <bug-31507-4717-wpw2AdEgET@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31507-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31507
--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Luis Machado from comment #10)
> Ok. This doesn't reproduce for me even if I run it 1000 times.
That's unfortunate.
Let me try to describe the setup, in case that helps in any way:
- lenovo ideapad 3 chromebook, SOC mt8183 (4 Cortex-A73, 4 Cortex-A53), 4GB RAM
- debian 12, installed from
https://github.com/hexdump0815/imagebuilder/blob/main/systems/chromebook_kukui/readme.md
- system up-to-date
- uname -a: Linux changeme 6.1.51-stb-mt8+ #1 SMP PREEMPT
Tue Sep 5 16:08:26 CEST 2023 aarch64 GNU/Linux
- ldd (Debian GLIBC 2.36-9+deb12u4) 2.36
- gcc version 12.2.0 (Debian 12.2.0-14)
- GNU assembler (GNU Binutils for Debian) 2.40
- gdb build with -O0 -g -fuse-ld=mold
- build at commit 6549a232d25 ("Fix compiling bfd/vms-lib.c for a 32-bit
host.")
I tried my usual tricks of "taskset -c 0" and "stress -c 8", but found that
this makes the fail less likely.
I haven't been able to reproduce on either pinebook pro (running manjaro) or m1
macbook (running fedora asahi remix).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-18 17:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 12:32 [Bug gdb/31507] New: " vries at gcc dot gnu.org
2024-03-18 14:03 ` [Bug gdb/31507] " vries at gcc dot gnu.org
2024-03-18 14:08 ` vries at gcc dot gnu.org
2024-03-18 14:08 ` vries at gcc dot gnu.org
2024-03-18 14:10 ` vries at gcc dot gnu.org
2024-03-18 14:55 ` vries at gcc dot gnu.org
2024-03-18 15:08 ` vries at gcc dot gnu.org
2024-03-18 15:11 ` [Bug tdep/31507] " vries at gcc dot gnu.org
2024-03-18 15:21 ` luis.machado at arm dot com
2024-03-18 15:21 ` luis.machado at arm dot com
2024-03-18 15:23 ` luis.machado at arm dot com
2024-03-18 17:20 ` luis.machado at arm dot com
2024-03-18 17:49 ` vries at gcc dot gnu.org [this message]
2024-03-18 18:05 ` luis.machado at arm dot com
2024-03-19 7:20 ` vries at gcc dot gnu.org
2024-03-19 8:13 ` luis.machado at arm dot com
2024-03-22 13:30 ` luis.machado at arm dot com
2024-05-06 12:09 ` 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-31507-4717-wpw2AdEgET@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).