This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [Patch] Microblaze: Port of Linux gdbserver
- From: Ajit Kumar Agarwal <ajit dot kumar dot agarwal at xilinx dot com>
- To: Pedro Alves <palves at redhat dot com>, Michael Eager <eager at eagercon dot com>, Joel Brobecker <brobecker at adacore dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, Vinod Kathail <vinodk at xilinx dot com>, Vidhumouli Hunsigida <vidhum at xilinx dot com>, "Nagaraju Mekala" <nmekala at xilinx dot com>
- Date: Thu, 18 Dec 2014 16:53:17 +0000
- Subject: RE: [Patch] Microblaze: Port of Linux gdbserver
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=pass (sender IP is 149.199.60.83) smtp dot mailfrom=ajit dot kumar dot agarwal at xilinx dot com;
- References: <25de23b98e054fd291ea232d10f2800c at BN1BFFO11FD018 dot protection dot gbl> <5436B7D0 dot 9060004 at eagercon dot com> <d0a23ff7601a4dbcab91d5b680bc2e13 at BY2FFO11FD017 dot protection dot gbl> <543E7630 dot 5060001 at redhat dot com> <99de529c620a4bb0a118a9fc39ae6ad0 at BY2FFO11FD008 dot protection dot gbl> <548F2240 dot 7020700 at redhat dot com> <b1a42502cd1843449e5668728141f5ed at BY2FFO11FD059 dot protection dot gbl> <5492BA45 dot 8090205 at redhat dot com>
-----Original Message-----
From: Pedro Alves [mailto:palves@redhat.com]
Sent: Thursday, December 18, 2014 4:58 PM
To: Ajit Kumar Agarwal; Michael Eager; Joel Brobecker
Cc: gdb-patches@sourceware.org; Vinod Kathail; Vidhumouli Hunsigida; Nagaraju Mekala
Subject: Re: [Patch] Microblaze: Port of Linux gdbserver
On 12/18/2014 08:56 AM, Ajit Kumar Agarwal wrote:
> From: Pedro Alves [mailto:palves@redhat.com] On 10/17/2014 08:22 PM,
> Ajit Kumar Agarwal wrote:
>
>> Gdb.base gdb testsuite is run and here is the status of gdb testsuite run for gdb.base.
>>
>> === gdb Summary ===
>>
>> # of expected passes 7804
>> # of unexpected failures 2263
>
>>> Over 2000 unexpected failures is not very reassuring though.
>>> Have you looked at the logs to get an idea of what might be broken?
>
> We have looked at the log files for the failures. Here are the main categories of the failure.
>
> 1. push_dummy_code is not implemented for Micro blaze port due to this there are 350+ failures.
>>Eh, no inferior function call support. Are you planning on implementing this?
Currently in the gdb microblaze-tdep.c, the following code is there for push_dummy_code.
static CORE_ADDR
microblaze_push_dummy_code (struct gdbarch *gdbarch, CORE_ADDR sp,
CORE_ADDR funcaddr,
struct value **args, int nargs,
struct type *value_type,
CORE_ADDR *real_pc, CORE_ADDR *bp_addr,
struct regcache *regcache)
{
error (_("push_dummy_code not implemented"));
return sp;
}
This causes the failures.
>>You can set gdb,cannot_call_functions in your board file to skip the affected tests meanwhile.
Thanks. I will use this option.
> 2. Failures for signals is around 357.
>>What sort of failures?
We are investigating the failures caused due to signal. Would let you know.
> 3. Watch point failures are around 817.
>>Set gdb,no_hardware_watchpoints in the board file.
Thanks. I will use this option.
>
> Main total categories of the failure = 376 + 357 + 817 = 1550.
>
> These failures are not because of gdbserver patch and they seem to exist prior to this patch.
Thanks & Regards
Ajit
Thanks,
Pedro Alves