From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Handle MIPS Linux SIGTRAP siginfo.si_code values
Date: Tue, 05 Apr 2016 16:57:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1604011401090.9427@tp.orcam.me.uk> (raw)
In-Reply-To: <56CE5CBD.9070105@redhat.com>
Hi Pedro,
> >> I've just finished testing it on s390 -- no regressions. I've
> >> pushed it in now, as is. I'll follow up with a new patch that makes
> >> gdb accept the anticipated new si_codes too.
> >
> > I'm fine with waiting for any outcome from a discussion with kernel
> > people before pushing such a change.
>
> Ack.
FYI, the kernel change has now made it upstream:
commit 3b143cca6e1397188f507a6c727f4108861ceb8b
Author: Maciej W. Rozycki <macro@imgtec.com>
Date: Fri Mar 4 01:44:28 2016 +0000
MIPS: traps: Correct the SIGTRAP debug ABI in `do_watch' and `do_trap_or_bp'
and will be present starting from Linux 4.6.0 release.
Maciej
next prev parent reply other threads:[~2016-04-05 16:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 16:44 Pedro Alves
2016-02-24 18:29 ` Maciej W. Rozycki
2016-02-24 18:51 ` Pedro Alves
2016-02-24 19:02 ` Luis Machado
2016-02-24 20:49 ` Maciej W. Rozycki
2016-02-24 21:10 ` Luis Machado
2016-02-24 20:39 ` Maciej W. Rozycki
2016-02-24 23:20 ` Pedro Alves
2016-02-24 23:37 ` [PATCH] MIPS/Linux: Also recognize TRAP_BRKPT and TRAP_HWBKPT Pedro Alves
2016-02-25 1:39 ` [PATCH] Handle MIPS Linux SIGTRAP siginfo.si_code values Maciej W. Rozycki
2016-02-25 1:45 ` Pedro Alves
2016-04-05 16:57 ` Maciej W. Rozycki [this message]
2016-04-15 23:17 ` Pedro Alves
2016-02-24 18:51 ` Luis Machado
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=alpine.DEB.2.00.1604011401090.9427@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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).