From: Jeff Kenton <jkenton@tilera.com>
To: Pedro Alves <palves@redhat.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, 07 May 2012 14:37:00 -0000 [thread overview]
Message-ID: <4FA7DE11.1000508@tilera.com> (raw)
In-Reply-To: <4F9EDD4B.3020409@redhat.com>
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 ...
>
A small number of tests are causing 75% of them (FAIL counts and test
names shown):
12 FAIL: gdb.base/break-interp.exp:
13 FAIL: gdb.base/args.exp:
14 FAIL: gdb.threads/thread-find.exp:
15 FAIL: gdb.opt/inline-cmds.exp:
15 FAIL: gdb.threads/tls.exp:
16 FAIL: gdb.threads/watchpoint-fork.exp:
18 FAIL: gdb.trace/save-trace.exp:
24 FAIL: gdb.threads/linux-dp.exp:
100 FAIL: gdb.threads/attach-into-signal.exp:
112 FAIL: gdb.cp/meth-typedefs.exp:
114 FAIL: gdb.base/sigstep.exp:
--jeff kenton
next prev parent reply other threads:[~2012-05-07 14:37 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
2012-05-07 14:37 ` Jeff Kenton [this message]
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=4FA7DE11.1000508@tilera.com \
--to=jkenton@tilera.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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