Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>,
	 Pierre Muller <muller@ics.u-strasbg.fr>
Subject: Re: [RFC] Remove last occurences of 	target_{insert/remove}_watchpoint
Date: Wed, 06 May 2009 17:14:00 -0000	[thread overview]
Message-ID: <200905061814.57665.pedro@codesourcery.com> (raw)
In-Reply-To: <20090506165425.GO10734@adacore.com>

On Wednesday 06 May 2009 17:54:25, Joel Brobecker wrote:
> > I've just ran this version through sparc solaris 8, and
> > it survived without regressions (although it looks like solaris test
> > results got much worse somewhere along these last weeks -- around
> > 1300 fails), and watchpoints still work.  Joel, would you like to
> > take a look at this and/or ran it on mips-irix?
> 
> I won't have much time in the next few weeks, unfortunately :-(.
> But I did run it through the testsuite. The results are really abysmal
> but no regression.

Okay, I'll check it in then.


>         # of expected passes            8361
>         # of unexpected failures        2114
>         # of unexpected successes       4
>         # of expected failures          33
>         # of known failures             29
>         # of unresolved testcases       33
>         # of untested testcases         72
>         # of unsupported tests          30

It seems most failures on solaris are related to a single problem, e.g., 

p/c fun()
$1 = 49 '<error reading variable>
(gdb) FAIL: gdb.base/call-sc.exp: p/c fun(); call call-sc-tc

>grep "error reading variable" gdb.log  | wc -l
1312

Looks like things are *really* broken.  That's around
as many failures as instances of that error:

# of expected passes            10933
# of unexpected failures        1337
# of expected failures          41
# of known failures             54
# of unresolved testcases       9
# of untested testcases         13
# of unsupported tests          67

Does this ring a bell?  I'll look at this at some point,
but probably only a couple of weeks or more from now.

-- 
Pedro Alves


  reply	other threads:[~2009-05-06 17:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 23:13 Pierre Muller
2009-04-23 18:36 ` Joel Brobecker
2009-04-29 23:00 ` Pedro Alves
2009-05-04 19:32   ` Pedro Alves
2009-05-06 16:54     ` Joel Brobecker
2009-05-06 17:14       ` Pedro Alves [this message]
2009-05-06 18:35         ` Joel Brobecker
2009-05-06 18:58           ` Pedro Alves

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=200905061814.57665.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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