From: Daniel Jacobowitz <drow@mvista.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:52:00 -0000 [thread overview]
Message-ID: <20021120185227.GD24089@nevyn.them.org> (raw)
In-Reply-To: <3DDBCB76.50205@redhat.com>
On Wed, Nov 20, 2002 at 12:50:46PM -0500, Andrew Cagney wrote:
> If you search the bug data base for high GDB PR's you'll see:
>
> PR Category State Priority Responsible Synopsis
> 378 gdb suspended high unassigned ``GNU/Linux'' ``Linux kernel''
> 394 gdb suspended high unassigned GDB 5.1.1 contains intl/ droppings
> 527 gdb suspended high unassigned GDB 5.2 incompatibilities with GNU
> textutils 2.0.21 in POSIX mode
> 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).
> 725 gdb open high unassigned Crash using debug target and regcaches (in
> 5.3 branch?)
> 763 gdb open high unassigned gdb 5.2 removes the conditional breakpoints
> 840 gdb suspended high unassigned Expect on GDB 5.3 branch doesn't build
> on IRIX 6.5
>
> It is these (actually the non-suspended ones) that I'm trying to get
> flushed.
>
> Of most concern are 708 and 676. They both indicate something failing the:
>
> ./configure
> make
> ./gdb/gdb ./gdb/gdb
> (gdb) b main
> (gdb) run
>
> release criteria :-(
I hit gdb/708 on HP/UX... it's really not that complicated to fix, I
don't think...
Of course trying to reproduce it I can't even build the snapshot; it
tries to make distclean in itcl.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-20 18:52 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
2002-11-20 10:52 ` Daniel Jacobowitz [this message]
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=20021120185227.GD24089@nevyn.them.org \
--to=drow@mvista.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