24h call for gdb-7.2.1 release

Joel Brobecker brobecker@adacore.com
Tue Dec 14 05:23:00 GMT 2010


> I have been faced downstream with various GDB crashes fixed by Pedro's:
> 	http://sourceware.org/bugzilla/show_bug.cgi?id=11371
> 
> Just the backport is not clean much so probably let it miss 7.2.1.

We're going to have to wait a little to evaluate a little more some
crashes in MI that Mark reported. So we also have time to look at this.

I'm not sure what the problem with the backport might be. I tried
cherry-picking the patch, and the only conflicts were in the ChangeLog
files (we are going to have to get rid of those, one of these days).
So the patch applies cleanly for me.

The problem that I see, then, is evaluating the risk of putting
this change in the branch. It's pretty large, and could potentially
contaminate all breakpoints, but should be limited to watchpoints.
It's been in HEAD since Aug, so 4 months, now. Do we know of any
problem that was introduced by this patch?  If not, then I'm OK with
putting it in 7.2.1, fixing any problem with a 7.2.2 if necessary.

-- 
Joel



More information about the Gdb-patches mailing list