From: Hui Zhu <teawater@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: time to create the gdb-7.0.1 release (?)
Date: Fri, 18 Dec 2009 08:52:00 -0000 [thread overview]
Message-ID: <daef60380912180051w3679cbefy7d97455786d1ad92@mail.gmail.com> (raw)
In-Reply-To: <20091218061736.GV2804@adacore.com>
Hi Joel,
Sorry that I have to be the trouble guy.
http://sourceware.org/ml/gdb-patches/2009-12/msg00010.html
This bug fix is still waiting review.
Thanks,
Hui
On Fri, Dec 18, 2009 at 14:17, Joel Brobecker <brobecker@adacore.com> wrote:
> Hello,
>
> According to our suggested schedule, yesterday (Dec 17) was the time
> we were hoping to produce gdb-7.0.1. Looking at the ChangeLog, here
> is the list of changes:
>
> - Fix a build compilation on IRIX 5.3:
> 2009-11-23 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
> * dwarf2read.c [HAVE_MMAP] (MAP_FAILED): Define if missing.
>
> - Add support for Thumb2 debugging:
> 2009-11-13 Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>
> Backport from mainline.
> 2009-07-28 Daniel Jacobowitz <dan@codesourcery.com>
>
> * arm-tdep.c (arm_push_dummy_call): Set the low bit of LR for
> a Thumb entry point.
> (thumb_get_next_pc): Handle Thumb-2 and ARM v6 instructions.
> Refuse to single step into IT blocks.
>
> 2009-10-28 Daniel Jacobowitz <dan@codesourcery.com>
> Reported by Antti Hatala <ahatala@nvidia.com>
> * arm-tdep.c (thumb_get_next_pc): Limit check to IT instructions
> correctly.
>
> - Fix a crash on solaris when reading symbols:
> 2009-10-22 Paul Pluzhnikov <ppluzhnikov@google.com>
> PR gdb/10819
> * dwarf2-frame.c (find_cie): Don't call bsearch on empty cie_table.
> * objfiles.c (find_pc_section): Likewise.
> (update_section_map): Don't allocate empty table.
>
> - I think the following change is mostly cosmetic:
> 2009-10-19 Don Lee <don.lee@sunplusct.com>
> * score-tdep.c: Delete some simulator dependent codes.
> * score-tdep.h: Delete some simulator dependent macro definitions.
>
> - Fix a build failure on newer versions of FreeBSD:
> 2008-10-16 Steven G. Kargl <kargl@gcc.gnu.org> (tiny patch)
> * amd64fbsd-nat.c (amd64fbsd_supply_pcb): Conditionally compile in
> support for pcb->pcb_{fs,ds,es,gs} on FreeBSD older than 8.0.
>
> - GDB SEGV due to stack overflow:
> 2009-10-08 Paul Pluzhnikov <ppluzhnikov@google.com>
> PR gdb/10457
> * elfread.c (elf_symtab_read): Don't use alloca in a loop.
>
> There is also a change in the documentation:
>
> 2009-10-04 Pedro Alves <pedro@codesourcery.com>
> * gdb.texinfo (Remote Protocol): Don't mention vCont;T.
>
> Anything else that should go in that (corrective) release?
>
> --
> Joel
>
next prev parent reply other threads:[~2009-12-18 8:52 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 [this message]
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
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=daef60380912180051w3679cbefy7d97455786d1ad92@mail.gmail.com \
--to=teawater@gmail.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