From: "Maciej W. Rozycki" <macro@imgtec.com>
To: Pedro Alves <palves@redhat.com>
Cc: Luis Machado <lgustavo@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH, v2] Expect SI_KERNEL or TRAP_BRKPT si_code values for MIPS breakpoint traps
Date: Mon, 22 Feb 2016 16:19:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1602221612230.15885@tp.orcam.me.uk> (raw)
In-Reply-To: <56CB0A42.70507@redhat.com>
On Mon, 22 Feb 2016, Pedro Alves wrote:
> I'd like to have a short paragraph in linux-nat.h about MIPS's behavior,
> below the ppc comment. If you look at the x86 table above, which cases get
> SI_KERNEL, and which don't? Single-step is not applicable, since the
> MIPS doesn't handle single-stepping itself (IIRC), but do we also get
> SI_KERNEL hardware bps and watchpoints, for example?
As I previously noted the MIPS Linux port currently does not support
hardware breakpoints even though hardware may have them implemented
(they're optional). Only hardware watchpoints are supported right now.
You are right in that there's no OS single-stepping support defined in
the MIPS architecture and consequently Linux cannot support it on the MIPS
target. Only JTAG single-stepping is possible with MIPS hardware.
Maciej
next prev parent reply other threads:[~2016-02-22 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 12:57 Luis Machado
2016-02-22 13:16 ` Pedro Alves
2016-02-22 16:19 ` Maciej W. Rozycki [this message]
2016-02-24 11:57 ` Pedro Alves
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.1602221612230.15885@tp.orcam.me.uk \
--to=macro@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--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