thirty-third thread == kaput

Jeffrey W. Baker jwbaker@acm.org
Wed Apr 18 11:04:00 GMT 2001


On Tue, 17 Apr 2001, Kevin Buettner wrote:

> There is a patch to fix this problem.  It was posted early last
> October.  See...
>
>     http://sources.redhat.com/ml/gdb-patches/2000-10/msg00014.html
>
> Unfortunately, it no longer applies cleanly to the current sources.
>
> I would really, really like to get this patch into the mainline
> sources, but I'm quite busy at the moment and haven't been able
> to find much time to work on it.

I'll take a look at it tonight, after I get home.  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.  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.

-jwb



More information about the Gdb mailing list