From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc@vger.kernel.org
Subject: Re: Running the gdb 7.12.1 testsuite breaks kernel 4.13.8 on C8000
Date: Wed, 17 Jul 2019 19:52:20 +0200 [thread overview]
Message-ID: <1957442.0sSArhqTEx@daneel.sf-tec.de> (raw)
In-Reply-To: <5e2ad677-7062-98d2-a6c5-577df02132d4@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Helge wrote:
> Hi Rolf,
>
> On 02.07.19 17:59, Helge Deller wrote:
> >>> This seems to be a minimal reproducer:
> >>> https://481768.bugs.gentoo.org/attachment.cgi?id=361728
> >
> > That's a REALLY nasty bug!
>
> I think I finally fixed the issues for 32- and 64-bit kernels.
>
> Can you please test the three patches in my ptrace-bugfix3 git tree?
> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/log/
> ?h=ptrace-bugfix3
I applied them on top of 5.2.0 and tested it on my C8000, it survived the
whole gdb 8.1.2 testsuite. The results are horrible, but the machine is still
up and running, just a couple of these:
[ 4481.730278] INEQUIVALENT ALIASES 0x41000000 and 0x42e81000 in file kill-
detach-inferiors-cmd
[ 8944.224759] INEQUIVALENT ALIASES 0x41ed2000 and 0x4171c000 in file multi-
attach
So feel free to add my Tested-by.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-07-17 17:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 8:59 Running the gdb 7.12.1 testsuite breaks kernel 4.13.8 on C8000 Rolf Eike Beer
2018-01-25 13:01 ` John David Anglin
2018-01-25 15:36 ` Rolf Eike Beer
2018-01-26 22:31 ` Helge Deller
2018-01-27 17:42 ` Rolf Eike Beer
2018-01-27 18:41 ` Helge Deller
2018-01-28 19:01 ` John David Anglin
2019-06-30 10:05 ` Rolf Eike Beer
2019-06-30 13:43 ` Rolf Eike Beer
2019-06-30 19:59 ` Helge Deller
2019-07-02 15:59 ` Helge Deller
2019-07-16 20:01 ` Helge Deller
2019-07-17 17:52 ` Rolf Eike Beer [this message]
2019-07-17 18:13 ` John David Anglin
2019-07-17 21:00 ` Helge Deller
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=1957442.0sSArhqTEx@daneel.sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-parisc@vger.kernel.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