Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: "Jeffrey W. Baker" <jwbaker@acm.org>
Cc: <gdb@sources.redhat.com>
Subject: Re: thirty-third thread == kaput
Date: Wed, 25 Apr 2001 16:52:00 -0000	[thread overview]
Message-ID: <1010425235153.ZM16223@ocotillo.lan> (raw)
In-Reply-To: <Pine.LNX.4.33.0104181059580.3747-100000@heat.gghcwest.com>

On Apr 18, 11:04am, Jeffrey W. Baker wrote:

> Do you think the patch doesn't apply because of major changes to
> data or algorithms, or just because code has moved around?  The
> patch is enormous and hairy.

Mostly due to code shifting a bit or new code being added.  There
were also rejects due to some files being obsoleted.

> As an outsider, I would say that the best strategy is to get the
> patch to where it applies, compiles, and runs, then commit it ASAP. 
> That will probably break GDB for a while, but it means that this
> important feature will actually get fixed.  Otherwise, it gets
> easier over time to just put off the fix because it becomes harder
> and harder to do.

I'm working on it again and have a patch out which should apply
cleanly.  See:

    http://sources.redhat.com/ml/gdb-patches/2001-04/msg00240.html

I'm going to be committing the patch in phases.  See the introductory
text to the patch for more details.

Kevin


      reply	other threads:[~2001-04-25 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17  9:24 Jeffrey W. Baker
2001-04-17 23:51 ` Kevin Buettner
2001-04-18 11:04   ` Jeffrey W. Baker
2001-04-25 16:52     ` Kevin Buettner [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=1010425235153.ZM16223@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=jwbaker@acm.org \
    /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