From: Ajit Kumar Agarwal <ajit.kumar.agarwal@xilinx.com>
To: Michael Eager <eager@eagercon.com>,
Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Vinod Kathail <vinodk@xilinx.com>,
Vidhumouli Hunsigida <vidhum@xilinx.com>,
"Nagaraju Mekala" <nmekala@xilinx.com>
Subject: RE: [Patch, microblaze]: Port of Linux gdbserver
Date: Tue, 16 Sep 2014 06:42:00 -0000 [thread overview]
Message-ID: <daf38849-83e4-44a7-8903-a5251b5bbbbd@BY2FFO11FD021.protection.gbl> (raw)
In-Reply-To: <54131362.1050009@eagercon.com>
-----Original Message-----
From: Michael Eager [mailto:eager@eagercon.com]
Sent: Friday, September 12, 2014 9:08 PM
To: Ajit Kumar Agarwal; Joel Brobecker
Cc: gdb-patches@sourceware.org; Vinod Kathail; Vidhumouli Hunsigida; Nagaraju Mekala
Subject: Re: [Patch, microblaze]: Port of Linux gdbserver
On 09/12/14 01:38, Ajit Kumar Agarwal wrote:
> Forget to attach the Patch Resending it again.
>
> With feedback comments incorporated, Please find the updated patch.
Again, please do not top post.
Please edit your posts. There is no need to include multiple copies of the ChangeLog.
> [Patch, microblaze]: Port of Linux gdbserver
>
> This patch is the port of Linux gdbserver.
>
> gdb/ChangeLog:
> 2014-10-12 Ajit Agarwal <ajitkum@xilinx.com>
>
> * configure.tgt (build_gdbserver): New Definition.
> * features/microblaze-linux-core.xml: New file.
> * features/microblaze-linux-stack-protect.xml: New file.
> * features/microblaze-linux-stack-protect.c: New file.
>>This is identical to microblaze-with-stack-protect.c. Both specify tdesc_create_feature (result, "org.gnu.gdb.microblaze.core");
>>Why is this needed?
This is needed as gdbserver code expects the register pc as "pc" instead of "rpc" for baremetel. The microblaze-linux-core.xml is changed from "rpc" to "pc" for gdbserver code to work.
>
> gdb/gdbserver/ChangeLog:
>
> * gdbserver/Makefile.in (microblaze-linux.c): New target.
> * gdbserver/configure.srv (microblaze*-*-linux*): New target.
> * gdbserver/linux-microblaze-low.c: New file.
>
> Signed-off-by:Ajit Agarwal ajitkum@xilinx.com
>>What are the results of running the gdb regression test suite using gdbserver on the target after applying this patch?
This patch requires the below patches which are already sent to FSF to be applied for the expected results with gdb regression testsuite.
The details and the related reasons are given below.
[Patch, microblaze] Add little-endian breakpoint.
[Patch, microblaze]: Add support of microblaze software single stepping
The above patches were already sent to FSF and are yet to be applied.
[Patch,microblaze]: Add support linux_memory_remove_breakpoints.
As suggested by Joel to not to mix the gdbserver patch with gdb patch, I will be sending the patch "Add Support linux_memory_remove_breakpoints" separately.
Without the above patches and running the gdb regression testsuite(gdb.base) gives bad testsuite results.
Hence the gdb testsuite is stopped in between.
warning: Remote failure reply: E01
Ignoring packet error, continuing...
FAIL: gdb.base/annota1.exp: print array (timeout)
Due to this error the subsequent testcases fails and following results were obtained.
=== gdb Summary ===
# of expected passes 67
# of unexpected failures 106
# of expected failures 1
# of unresolved testcases 6
# of untested testcases 4
# of unsupported tests 96
With the above mentioned gdb patches and the gdbserver patch, below are the results. All the executables are little endian binaries compiled with microblazeel-xilinux-linux-gnu.
=== gdb Summary ===
# of expected passes 8146
# of unexpected failures 2470
# of unexpected successes 2
# of expected failures 6
# of known failures 21
# of unresolved testcases 28
# of untested testcases 44
# of unsupported tests 125
Thanks & Regards
Ajit
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2014-09-16 6:42 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 10:14 Ajit Kumar Agarwal
2014-09-10 13:31 ` Michael Eager
2014-09-10 13:46 ` Joel Brobecker
2014-09-10 14:23 ` Ajit Kumar Agarwal
2014-09-10 14:39 ` Michael Eager
2014-09-10 14:59 ` Ajit Kumar Agarwal
2014-09-10 15:12 ` Ajit Kumar Agarwal
2014-09-10 15:27 ` Michael Eager
2014-09-10 15:30 ` Ajit Kumar Agarwal
2014-09-10 15:35 ` Michael Eager
2014-09-10 15:51 ` Ajit Kumar Agarwal
2014-09-10 14:43 ` Joel Brobecker
2014-09-10 15:04 ` Ajit Kumar Agarwal
2014-09-10 15:54 ` Joel Brobecker
2014-09-10 16:10 ` Ajit Kumar Agarwal
2014-09-12 8:01 ` Ajit Kumar Agarwal
2014-09-12 8:39 ` Ajit Kumar Agarwal
2014-09-12 15:38 ` Michael Eager
2014-09-16 6:42 ` Ajit Kumar Agarwal [this message]
2014-09-16 12:06 ` Michael Eager
2014-09-17 9:36 ` Ajit Kumar Agarwal
2014-09-17 14:12 ` Michael Eager
2014-09-16 17:04 ` Pedro Alves
2014-09-17 6:16 ` Ajit Kumar Agarwal
2014-09-17 8:15 ` Pedro Alves
2014-09-17 8:20 ` Ajit Kumar Agarwal
2014-09-23 12:49 ` Ajit Kumar Agarwal
2014-09-30 11:43 ` Pedro Alves
2014-09-30 13:27 ` Ajit Kumar Agarwal
2014-09-30 13:37 ` Pedro Alves
2014-09-30 14:21 ` Ajit Kumar Agarwal
2014-10-08 13:52 [Patch] Microblaze: " Ajit Kumar Agarwal
2014-10-09 16:29 ` Michael Eager
2014-10-09 18:54 ` Ajit Kumar Agarwal
2014-10-09 23:42 ` Michael Eager
2014-10-13 16:00 ` Ajit Kumar Agarwal
2014-10-13 17:49 ` Michael Eager
2014-10-14 3:03 ` Ajit Kumar Agarwal
2014-10-14 15:07 ` Michael Eager
2014-10-14 15:33 ` Ajit Kumar Agarwal
2014-10-14 15:42 ` Ajit Kumar Agarwal
2014-10-15 13:27 ` Pedro Alves
2014-10-17 19:22 ` Ajit Kumar Agarwal
2014-12-15 18:02 ` Pedro Alves
2014-12-15 18:13 ` Michael Eager
2014-12-18 8:58 ` Ajit Kumar Agarwal
2014-12-18 16:10 ` Michael Eager
2014-12-18 8:57 ` Ajit Kumar Agarwal
2014-12-18 11:28 ` Pedro Alves
2014-12-18 16:53 ` Ajit Kumar Agarwal
2014-12-18 17:40 ` Pedro Alves
2014-12-19 8:27 ` Ajit Kumar Agarwal
2014-12-19 10:56 ` Pedro Alves
2014-12-19 10:26 ` Ajit Kumar Agarwal
2014-12-19 11:02 ` Pedro Alves
2014-12-19 18:06 ` Ajit Kumar Agarwal
2014-11-26 12:13 ` Ajit Kumar Agarwal
2014-12-15 16:08 ` Ajit Kumar Agarwal
2014-10-08 14:59 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=daf38849-83e4-44a7-8903-a5251b5bbbbd@BY2FFO11FD021.protection.gbl \
--to=ajit.kumar.agarwal@xilinx.com \
--cc=brobecker@adacore.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
--cc=nmekala@xilinx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).