Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: howarth@bromo.med.uc.edu (Jack Howarth)
Cc: brobecker@adacore.com (Joel Brobecker),
	tromey@redhat.com (Tom Tromey),
	        ppluzhnikov@google.com (Paul Pluzhnikov),
	        ASinha@zeugmasystems.com (Anirban Sinha),
	gdb@sourceware.org,         msnyder@vmware.com (Michael Snyder)
Subject: Re: FW: gdb seems to be broken on darwin 10.5.8 and later
Date: Mon, 05 Oct 2009 22:13:00 -0000	[thread overview]
Message-ID: <200910052213.n95MDfnW004838@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20091005130310.GA25614@bromo.med.uc.edu> from "Jack Howarth" at Oct 05, 2009 09:03:10 AM

Jack Howarth wrote:

>   I ran the make check on gdb cvs last night (without an ada compiler
> installed) and the test results seemed reasonable. Does gdb have anything
> like the contrib/test_summary script from gcc so that a shorter summary
> can be generated for the gdb-testers mailing list? I thought I would
> post some full test results in case any particular failures jumped out
> as being low hanging fruit for fixing.

You can simply use GCC's test_summary script; this works just fine
for GDB as well ...

Bye,
Ulrich


-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


      parent reply	other threads:[~2009-10-05 22:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 20:37 Anirban Sinha
2009-10-01  3:34 ` Paul Pluzhnikov
2009-10-02  1:55   ` Jack Howarth
2009-10-02  2:13     ` Paul Pluzhnikov
2009-10-02 15:37       ` Joel Brobecker
2009-10-02 16:03         ` Tom Tromey
2009-10-02 16:21           ` Jack Howarth
2009-10-05  2:57           ` Joel Brobecker
2009-10-05 13:03             ` Jack Howarth
2009-10-05 16:54               ` Joel Brobecker
2009-10-05 22:13               ` Ulrich Weigand [this message]

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=200910052213.n95MDfnW004838@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=ASinha@zeugmasystems.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=howarth@bromo.med.uc.edu \
    --cc=msnyder@vmware.com \
    --cc=ppluzhnikov@google.com \
    --cc=tromey@redhat.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