Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jeff Kenton <jkenton@tilera.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add support for Tilera TILE-Gx processor (part 2/2: gdb)
Date: Mon, 30 Apr 2012 19:17:00 -0000	[thread overview]
Message-ID: <4F9EE28C.6010505@redhat.com> (raw)
In-Reply-To: <4F9EDF47.1080904@tilera.com>

On 04/30/2012 07:51 PM, Jeff Kenton wrote:

> On 04/30/2012 02:43 PM, Pedro Alves wrote:
>> I meant to reply to this before, but it slipped...
>>
>> On 04/20/2012 04:23 PM, Jeff Kenton wrote:
>>
>>                  === gdb Summary ===
>>
>> # of expected passes            18181
>> # of unexpected failures        625
>>
>> Did you look at what is causing these hundreds of failures?  Although there
>> are thousands of passes, such high failure rate is usually indicative of
>> something badly borked.  You'd be surprised at how far in testsuite results
>> you can get with a gdb that manages to loads programs, but is a brick
>> at actually debugging live programs ...
>>
>>> # of expected failures          100
>>> # of known failures             59
>>> # of untested testcases         12
>>> # of unresolved testcases       4
>>> # of unsupported tests          118
>>> /gdb_tests/gdb/build/gdb/testsuite/../../gdb/gdb version  7.4.50.20120410 -nw -nx -data-directory /gdb_tests/gdb/build/gdb/testsuite/../data-directory
>>
> 
> We use it on production systems, so lots of things work.  Checking the failures is on my list of things to do.  Is there a target failure threshhold we need to hit before our GDB is accepted, or can we submit what we have (with the fixes you specified) and work on the remaining test suite failures afterwards?


There's no threshold, and certainly zero fails are not expected.  Not even the
most maintained ports get that far, unfortunately.  So we'll accept the port anyway.
But I'd be happier if at least you had browsed the gdb.sum/gdb.log for obvious
issues, and at least (any) internal-errors that show up are given some
consideration.

-- 
Pedro Alves


  reply	other threads:[~2012-04-30 19:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 20:18 Jeff Kenton
2012-04-20 15:18 ` Yao Qi
2012-04-20 15:30   ` Jeff Kenton
2012-04-30 18:44     ` Pedro Alves
2012-04-30 19:06       ` Jeff Kenton
2012-04-30 19:17         ` Pedro Alves [this message]
2012-05-07 14:37       ` Jeff Kenton
2012-05-07 15:34         ` Yao Qi
2012-04-23 15:05   ` Jeff Kenton
2012-04-24 21:25     ` Joel Brobecker
2012-04-24 21:41       ` Joel Brobecker
2012-04-25  1:38     ` Yao Qi
2012-04-20 19:05 ` Tom Tromey

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=4F9EE28C.6010505@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jkenton@tilera.com \
    --cc=yao@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