From: Michael Eager <eager@eagercon.com>
To: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>,
Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>,
Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
Nagaraju Mekala <nmekala@xilinx.com>
Subject: Re: [Patch, microblaze]: Add support of microblaze software single stepping
Date: Fri, 11 Jul 2014 20:58:00 -0000 [thread overview]
Message-ID: <53C041BD.4060303@eagercon.com> (raw)
In-Reply-To: <ab8da1f0-cade-46f8-97e0-888662ff368e@BY2FFO11FD002.protection.gbl>
On 07/11/14 12:34, Ajit Kumar Agarwal wrote:
>
>>> Please also explain how this patch was tested.
>
> The changes were tested with the application for barematel with remote debug with XMD debugger( internal to Xilinx)which connects to the target and opens the gdbserver connection. Single stepping command were used for next_pc in straight line code, with imm instruction and the branch with delay Slot.
Your terminology may be a bit confusing. Gdbserver
is a program (part of GDB) which runs on a platform (e.g.
Linux), and which implements the GDB Remote Serial Protocol.
XMD does not run gdbserver. It has an independent implementation
of the GDB Remote Serial Protocol. It would be better to
say that XMD is a remote stub.
Please provide a disassembly of the test case and
a log of the commands to gdb and gdb's output, showing
stepping over imm and delay slot instructions.
Is there a test case which shows single stepping failing
without the patch?
Even better would be to update the gdb regression
test suite with the test case.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2014-07-11 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-06 6:13 Ajit Kumar Agarwal
2014-07-07 14:56 ` Joel Brobecker
2014-07-11 12:53 ` Ajit Kumar Agarwal
2014-07-11 14:05 ` Joel Brobecker
2014-07-11 14:42 ` Ajit Kumar Agarwal
2014-07-11 19:44 ` Ajit Kumar Agarwal
2014-07-11 20:58 ` Michael Eager [this message]
2014-07-14 11:42 ` Ajit Kumar Agarwal
2014-09-15 16:06 ` Michael Eager
2014-07-20 14:03 ` Ajit Kumar Agarwal
-- strict thread matches above, loose matches on Subject: below --
2014-06-20 6:10 Ajit Kumar Agarwal
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=53C041BD.4060303@eagercon.com \
--to=eager@eagercon.com \
--cc=ajit.kumar.agarwal@xilinx.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=nmekala@xilinx.com \
--cc=palves@redhat.com \
--cc=vidhum@xilinx.com \
--cc=vinodk@xilinx.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