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 external/31442] [gdb/external, arm, SIGILL] FAIL: gdb.threads/sigstep-threads.exp: step 92
Date: Tue, 05 Mar 2024 16:41:19 +0000	[thread overview]
Message-ID: <bug-31442-4717-hc8m7FUG4W@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31442-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31442

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |MOVED
             Status|NEW                         |RESOLVED
            Summary|[gdb/tdep, arm, SIGILL]     |[gdb/external, arm, SIGILL]
                   |FAIL:                       |FAIL:
                   |gdb.threads/sigstep-threads |gdb.threads/sigstep-threads
                   |.exp: step 92               |.exp: step 92
          Component|tdep                        |external

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> I looked into upgrading the kernel to 6.1, but it seems that this is
> difficult because /boot is read-only due to being flash, so I'm avoiding
> that for now.

I gave it a try, and ... was left with an non-booting system.

I managed to recover by booting from an sd card (which involved opening the
laptop to recover the micro sd card that slid next to rather than into the
slot).

Then I managed to overwrite the broken installation on the hard-disk and chose
the manjaro distro, because it's supposedly the best supported distro for
pinebook pro.  That got me a 6.1.x kernel, which after upgrading got me a 6.6.7
kernel. 

The manjaro install also got me a 64-bit kernel + 64-bit user land.

I managed to build a chroot with 32-bit debian, which is about as close as I
can get to the old 64-bit kernel + 32-bit userland setup. [ I used arch-chroot,
hand-edited to unset pid_unshare and mount_unshare, otherwise we run into
warnings due to not finding /proc/PID/mem. ]

I ran this test-case a 100 times, and the problem doesn't reproduce.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2024-03-05 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 12:33 [Bug tdep/31442] New: [gdb/tdep, " vries at gcc dot gnu.org
2024-03-03 11:01 ` [Bug tdep/31442] " vries at gcc dot gnu.org
2024-03-05 16:41 ` vries at gcc dot gnu.org [this message]

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-31442-4717-hc8m7FUG4W@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).