From: Yao Qi <qiyaoltc@gmail.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [patch 1/3, nios2] revert to using "trap 31" for breakpoints
Date: Tue, 28 Apr 2015 11:18:00 -0000 [thread overview]
Message-ID: <86egn4wlx4.fsf@gmail.com> (raw)
In-Reply-To: <55393F7F.40004@codesourcery.com> (Sandra Loosemore's message of "Thu, 23 Apr 2015 12:52:47 -0600")
Sandra Loosemore <sandra@codesourcery.com> writes:
> -/* Implement the breakpoint_from_pc gdbarch hook. */
> +/* Implement the breakpoint_from_pc gdbarch hook.
> + Note that the Nios II ABI for Linux requires "trap 31"
> + as the breakpoint, and we use that consistently on all targets. */
Please quote the original statement from NIOS 2 ABI,
"Userspace programs should not use the break instruction and userspace
debuggers should not insert one."
and
"Userspace breakpoints are accomplished using the trap instruction with
immediate operand 31 (all ones)."
OK with this change.
--
Yao (齐尧)
next prev parent reply other threads:[~2015-04-28 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 18:49 [patch 0/3, nios2] unbreak nios2-linux-gnu GDB Sandra Loosemore
2015-04-23 18:53 ` [patch 1/3, nios2] revert to using "trap 31" for breakpoints Sandra Loosemore
2015-04-28 11:18 ` Yao Qi [this message]
2015-04-23 18:55 ` [patch 2/3, nios2] use PTRACE_GETREGSET/SETREGSET in gdbserver Sandra Loosemore
2015-04-28 11:29 ` Yao Qi
2015-04-28 11:31 ` Pedro Alves
2015-04-28 15:27 ` Sandra Loosemore
2015-04-23 19:01 ` [patch 3/3, nios2] fixes for new implementation of signal handler trampolines Sandra Loosemore
2015-04-23 19:11 ` Sandra Loosemore
2015-04-28 12:11 ` Yao Qi
2015-04-28 15:47 ` Sandra Loosemore
2015-04-28 11:15 ` [patch 0/3, nios2] unbreak nios2-linux-gnu GDB Yao Qi
2015-04-28 15:14 ` Sandra Loosemore
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=86egn4wlx4.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sandra@codesourcery.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