* 24h call for gdb-7.2.1 release
@ 2010-12-13 10:25 Joel Brobecker
2010-12-13 18:50 ` Jan Kratochvil
0 siblings, 1 reply; 3+ messages in thread
From: Joel Brobecker @ 2010-12-13 10:25 UTC (permalink / raw)
To: gdb-patches
Hello everyone,
As far as I know, all identified patches have now been checked in
the 7.2 branch, so we should be ready to release 7.2.1. If no other
problem is brought to my attention, I will make the release either
tomorrow or Wed.
Note that, although I usually do not expect us to need a .2 minor
release, this is not excluded. If we find that this would be useful
for any reason, one can be added (even after the process for the next
major revision has been started).
--
Joel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 24h call for gdb-7.2.1 release
2010-12-13 10:25 24h call for gdb-7.2.1 release Joel Brobecker
@ 2010-12-13 18:50 ` Jan Kratochvil
2010-12-14 5:23 ` Joel Brobecker
0 siblings, 1 reply; 3+ messages in thread
From: Jan Kratochvil @ 2010-12-13 18:50 UTC (permalink / raw)
To: Joel Brobecker; +Cc: gdb-patches
Hi Joel,
On Mon, 13 Dec 2010 11:24:45 +0100, Joel Brobecker wrote:
> As far as I know, all identified patches have now been checked in
> the 7.2 branch, so we should be ready to release 7.2.1.
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.
Regards,
Jan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: 24h call for gdb-7.2.1 release
2010-12-13 18:50 ` Jan Kratochvil
@ 2010-12-14 5:23 ` Joel Brobecker
0 siblings, 0 replies; 3+ messages in thread
From: Joel Brobecker @ 2010-12-14 5:23 UTC (permalink / raw)
To: Jan Kratochvil; +Cc: gdb-patches
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-12-14 5:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-12-13 10:25 24h call for gdb-7.2.1 release Joel Brobecker
2010-12-13 18:50 ` Jan Kratochvil
2010-12-14 5:23 ` Joel Brobecker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox