From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26717 invoked by alias); 19 Dec 2014 11:02:47 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 26686 invoked by uid 89); 19 Dec 2014 11:02:46 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Fri, 19 Dec 2014 11:02:45 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sBJB2cHK019004 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 19 Dec 2014 06:02:39 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id sBJB2aoS027859; Fri, 19 Dec 2014 06:02:36 -0500 Message-ID: <549405CB.1030208@redhat.com> Date: Fri, 19 Dec 2014 11:02:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 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 References: <25de23b98e054fd291ea232d10f2800c@BN1BFFO11FD018.protection.gbl> <5436B7D0.9060004@eagercon.com> <543E7630.5060001@redhat.com> <99de529c620a4bb0a118a9fc39ae6ad0@BY2FFO11FD008.protection.gbl> <548F2240.7020700@redhat.com> <5492BA45.8090205@redhat.com> <81895ba3cb504c4b8a4365c3ffba0444@BY2FFO11FD051.protection.gbl> In-Reply-To: <81895ba3cb504c4b8a4365c3ffba0444@BY2FFO11FD051.protection.gbl> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-12/txt/msg00573.txt.bz2 On 12/19/2014 10:26 AM, Ajit Kumar Agarwal wrote: > -----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? > >>> You can set gdb,cannot_call_functions in your board file to skip the affected tests meanwhile. > >> 2. Failures for signals is around 357. > >>> What sort of failures? > >> 3. Watch point failures are around 817. > >>> Set gdb,no_hardware_watchpoints in the board file. > > Thanks. We have used the following gdb options as per your suggestions. > > set_board_info gdb,no_hardware_watchpoints 1 set_board_info gdb,cannot_call_functions 1 set_board_info gdb,nosignals 1 > To be clear, gdb,nosignals is for targets that truly have no concept of signals. A Linux port should not need that... It's probably masking out real problems. > The gdb summary for gdb.base is as follows: > > === gdb Summary === > > # of expected passes 6047 > # of unexpected failures 539 FYI, this is way higher than I'd expect after disabling all that functionality. > # of expected failures 17 > # of known failures 21 > # of unresolved testcases 26 > # of untested testcases 43 > # of unsupported tests 133 > > I will send the modified patch incorporating your comments. Thanks. Pedro Alves