public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28056] [11/12 Regression] linux-tdep.c:2550: internal-error: displaced_step_prepare_status linux_displaced_step_prepare on s390x-linux-gnu
Date: Wed, 07 Jul 2021 08:29:40 +0000	[thread overview]
Message-ID: <bug-28056-4717-SJO1XVn8Ld@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28056-4717@http.sourceware.org/bugzilla/>

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

--- Comment #8 from Matthias Klose <doko at debian dot org> ---
looking at a 20210706 build, the fix seems to work.  Unsure what I did wrong
yesterday.  So the fix would be needed on the trunk and the branch.

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

  parent reply	other threads:[~2021-07-07  8:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05  8:27 [Bug gdb/28056] New: " doko at debian dot org
2021-07-05  8:27 ` [Bug gdb/28056] " doko at debian dot org
2021-07-05 15:00 ` simark at simark dot ca
2021-07-05 18:14 ` simark at simark dot ca
2021-07-06  5:03 ` doko at debian dot org
2021-07-06  6:01 ` doko at debian dot org
2021-07-06 13:43 ` simark at simark dot ca
2021-07-06 16:12 ` doko at debian dot org
2021-07-06 16:42 ` simark at simark dot ca
2021-07-06 22:00 ` simark at simark dot ca
2021-07-07  8:29 ` doko at debian dot org [this message]
2021-07-07 12:58 ` simark at simark dot ca
2021-07-08 14:05 ` cvs-commit at gcc dot gnu.org
2021-07-08 14:06 ` cvs-commit at gcc dot gnu.org
2021-07-08 14:10 ` simark at simark dot ca
2021-07-11 14:30 ` brobecker at gnat dot com
2021-07-11 14:31 ` simark at simark dot ca

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-28056-4717-SJO1XVn8Ld@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).