From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [5.3] What's the hold up?
Date: Wed, 20 Nov 2002 10:43:00 -0000 [thread overview]
Message-ID: <20021120184342.GR1259@gnat.com> (raw)
In-Reply-To: <3DDBCB76.50205@redhat.com>
> 676 gdb analyzed high unassigned Alpha OSF1, gcc, internal GDB error in
> mdebugread
> 708 gdb open high unassigned Can't build 5.3 branch (and probably trunk).
[...]
> Of most concern are 708 and 676. They both indicate something failing the:
>
> ./configure
> make
> ./gdb/gdb ./gdb/gdb
> (gdb) b main
> (gdb) run
I don't think that 676 is any worse than before, so I would not hold up
5.3 for this PR. I just tried your release criteria on Tru64 4.0f and
5.1a, and the test passed...
My 2 cents...
--
Joel
next prev parent reply other threads:[~2002-11-20 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 9:50 Andrew Cagney
2002-11-20 10:43 ` Joel Brobecker [this message]
2002-11-20 10:52 ` Daniel Jacobowitz
2002-11-20 11:07 ` Daniel Jacobowitz
2002-11-20 13:41 ` Daniel Jacobowitz
2002-11-20 21:09 ` Andrew Cagney
2002-11-20 21:09 ` Andrew Cagney
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=20021120184342.GR1259@gnat.com \
--to=brobecker@gnat.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.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