From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6.3 branch 2004-10-16-ish
Date: Wed, 06 Oct 2004 18:58:00 -0000 [thread overview]
Message-ID: <4164401F.2030201@gnu.org> (raw)
In-Reply-To: <20041006175540.GB9904@nevyn.them.org>
> On Wed, Oct 06, 2004 at 01:38:22PM -0400, Andrew Cagney wrote:
>
>>> The two big lumps appear to have been swallowed - ada and ICU. There's
>>> still stuff floating around for instance:
>>>
>>> - end-of-life deprecated_registers
>>> - end-of-life xm file (that looks likely to slip)
>>>
>>> I might get bored and mark up gdb over the weekend the comming weekend.
>>> But others, such as the bfd stuff needed to de-hack vsyscall are going
>>> to have to slip out.
>
>
> Ignoring the de-hacking, how about actually connecting it?
Which system? It's already connected on i386 GNU/Linux right?
> I'm still waiting for the two corresponding failures in corefile.exp to
> go away.
The de-hack is to fix the failures on corefile and attach :-/
Andrew
next prev parent reply other threads:[~2004-10-06 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 17:41 Andrew Cagney
2004-10-06 17:48 ` Joel Brobecker
2004-10-06 17:56 ` Daniel Jacobowitz
2004-10-06 18:58 ` Andrew Cagney [this message]
2004-10-06 19:10 ` Daniel Jacobowitz
2004-10-25 9:43 ` Daniel Jacobowitz
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=4164401F.2030201@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).