From: Joel Brobecker <brobecker@adacore.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
aristovski@qnx.com, gdb-patches@sourceware.org
Subject: Re: [rfc v2][rft (procfs, nto-procfs)] Fix signal bypass heuristic with software single-step
Date: Wed, 27 Apr 2011 01:12:00 -0000 [thread overview]
Message-ID: <20110427011154.GA27627@adacore.com> (raw)
In-Reply-To: <201104051922.p35JMeFA006141@d06av02.portsmouth.uk.ibm.com>
> Joel, I was wondering if you still have some procfs-based machines
> (e.g. Solaris) where you could run a test?
I finally found the time to test this patch on mips-irix, and the
testsuite revealed no regression. I have a few FAIL that turned
into PASS, but these are thread testcases, so it could be by pure
accident. Sorry for taking so long for doing this...
Results on mips-irix are not as bad as I thought they might be.
I don't have a C++ compiler on this platform, so it accounts
for some of the failures. But otherwise, here are the totals:
# of expected passes 11461
# of unexpected failures 357
# of unexpected successes 3
# of expected failures 57
# of untested testcases 119
# of unresolved testcases 5
# of unsupported tests 56
--
Joel
next prev parent reply other threads:[~2011-04-27 1:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 1:54 [rfc][rft " Ulrich Weigand
2011-03-22 17:25 ` Pedro Alves
2011-03-24 16:39 ` Ulrich Weigand
2011-03-31 19:42 ` [rfc v2][rft " Ulrich Weigand
2011-04-04 9:47 ` Pedro Alves
2011-04-05 19:22 ` Ulrich Weigand
2011-04-05 19:33 ` Aleksandar Ristovski
2011-04-05 22:56 ` Ulrich Weigand
2011-04-06 1:37 ` Aleksandar Ristovski
2011-04-06 17:00 ` Ulrich Weigand
2011-04-26 17:34 ` Ulrich Weigand
2011-04-06 6:07 ` Joel Brobecker
2011-04-06 17:01 ` Ulrich Weigand
2011-04-27 1:12 ` Joel Brobecker [this message]
2011-04-27 13:31 ` Ulrich Weigand
2011-03-22 17:37 ` [rfc][rft " 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=20110427011154.GA27627@adacore.com \
--to=brobecker@adacore.com \
--cc=aristovski@qnx.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=uweigand@de.ibm.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