Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>,  gdb-patches@sourceware.org
Cc: Stan Shebs <stan@codesourcery.com>,
	 Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: [RFA] Darwin/x86 port (v2 - part 0)
Date: Fri, 14 Nov 2008 17:44:00 -0000	[thread overview]
Message-ID: <8C0C9EB8-A4C2-4C48-9A0E-8D79DF04AAF5@adacore.com> (raw)
In-Reply-To: <uhc6anx2p.fsf@gnu.org>


On Nov 14, 2008, at 4:31 PM, Eli Zaretskii wrote:
> I'd like to know whether there are any large sets of failed tests that
> have something in common (a.k.a. unsupported GDB features), before I
> make up my mind.

Sure.
I was using a wrong gdb (was work in progress).  New results are much  
better:

		=== gdb Summary ===

# of expected passes		10785
# of unexpected failures	653
# of expected failures		33
# of known failures		117
# of unresolved testcases	5
# of untested testcases		30
# of unsupported tests		59

There are a few obvious groups:
* unwinding through signals handlers doesn't work.
* shared libraries are not supported.  There are a few consequences:  
break printf doesn't work too.
* no core support
* no thread support
* call-sc doesn't work.

Tristan.



  reply	other threads:[~2008-11-14 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 10:14 Tristan Gingold
2008-11-13 15:11 ` Tristan Gingold
2008-11-13 19:41   ` Mark Kettenis
2008-11-13 20:40     ` Tristan Gingold
2008-11-13 21:41       ` Stan Shebs
2008-11-14 16:28         ` Tristan Gingold
2008-11-14 16:41           ` Stan Shebs
2008-11-14 17:04             ` Eli Zaretskii
2008-11-14 17:44               ` Tristan Gingold [this message]
2008-11-14 17:40             ` Joel Brobecker
2008-11-14 17:47               ` Mark Kettenis
2008-11-14 15:51 ` Eli Zaretskii

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=8C0C9EB8-A4C2-4C48-9A0E-8D79DF04AAF5@adacore.com \
    --to=gingold@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=stan@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