From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: time to create the gdb-7.0.1 release (?)
Date: Sat, 19 Dec 2009 18:03:00 -0000 [thread overview]
Message-ID: <20091219180214.GA13414@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20091218061736.GV2804@adacore.com>
Hi Joel,
On Fri, 18 Dec 2009 07:17:36 +0100, Joel Brobecker wrote:
> Anything else that should go in that (corrective) release?
http://sourceware.org/ml/gdb-patches/2009-11/msg00422.html
http://sourceware.org/ml/gdb-cvs/2009-11/msg00169.html
[commit] SEGV trying to complete "catch exception" command
* completer.c (complete_line_internal): Make sure the command
completer is not NULL before calling it.
http://sourceware.org/ml/gdb-patches/2009-11/msg00269.html
http://sourceware.org/ml/gdb-cvs/2009-11/msg00118.html
Re: [RFA] dcache invalidate fix
* dcache.c (dcache_block): Replace member newer with next,prev.
(dcache_struct): Delete member newest.
(block_func): New typedef.
(append_block, remove_block, for_each_block): New functions.
(invalidate_block, free_block): New functions.
(dcache_invalidate): Update
(dcache_invalidate_line, dcache_alloc): Update to use new list
accessors.
(dcache_free): Ditto. Fix memory leak.
Locking up GDB on ppc64 inferiors.
While this unchecked-in is less intrusive
http://sourceware.org/ml/gdb-patches/2009-11/msg00233.html
it forgot to update `dcache->newest'.
Optionally a set of testsuite results stabilization patches:
http://sourceware.org/ml/gdb-patches/2009-11/msg00594.html
http://sourceware.org/ml/gdb-cvs/2009-11/msg00233.html
Subject: [patch] testsuite: bigcore.exp fuzzy PASS message fix
http://sourceware.org/ml/gdb-patches/2009-11/msg00593.html
http://sourceware.org/ml/gdb-cvs/2009-12/msg00013.html
Subject: [patch] testcase: Fix spurious structs.exp FAILs
http://sourceware.org/ml/gdb-patches/2009-11/msg00573.html
http://sourceware.org/ml/gdb-cvs/2009-11/msg00232.html
Subject: [patch] testsuite fuzzy results fixup: foll-fork.exp
Regards,
Jan
next prev parent reply other threads:[~2009-12-19 18:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 6:17 Joel Brobecker
2009-12-18 7:44 ` Ralf Corsepius
2009-12-18 8:10 ` Joel Brobecker
2009-12-18 8:52 ` Hui Zhu
2009-12-18 8:56 ` Joel Brobecker
2009-12-18 9:02 ` Hui Zhu
2009-12-18 9:45 ` Joel Brobecker
2009-12-18 14:24 ` Jack Howarth
2009-12-18 14:33 ` Joel Brobecker
2009-12-18 17:35 ` Michael Snyder
2009-12-18 17:40 ` Joel Brobecker
2009-12-18 17:54 ` Michael Snyder
2009-12-19 18:03 ` Jan Kratochvil [this message]
2009-12-21 6:01 ` Joel Brobecker
2009-12-21 9:07 ` Jan Kratochvil
2009-12-20 20:27 ` Jan Kratochvil
2009-12-21 9:54 ` Vladimir Prus
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=20091219180214.GA13414@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.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