From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Ralf Corsepius <ralf.corsepius@rtems.org>,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: one week to gdb-7.6 release?
Date: Wed, 20 Mar 2013 17:08:00 -0000 [thread overview]
Message-ID: <5149EC84.7030008@oarcorp.com> (raw)
In-Reply-To: <20130320160032.GC5447@adacore.com>
On 3/20/2013 11:00 AM, Joel Brobecker wrote:
> Hello,
>
> We're about one week away from our tentative date for gdb-7.6 release,
> and I was wondering how we are doing, and whether there might be
> some issues that might prevent us from releasing around our planned
> date.
>
> I know of:
>
> * PR/15289 set remote hardware-watchpoint-limit" broken (zinteger commands)
> (regression)
> Easy to fix, or just revert the patch that caused the regression?
>
> * dv-sockser.o build issues in the sim.
> Looks like the thread lost steam a bit - can we stoke the fire again?
>
I am sorry. I am at an Open Group meeting this week and couldn't get a
checkout
until sourceware.org's hardware upgrade got source code repos available
again.
I just did a git clone and am working through the issues. I plan to send a
patch to common plus one per target simulator. Hopefully that will make
it easier to review and approve.
> Jan, not sure if some of the patches you posted for 7.6 are still
> pending?
>
> Thanks!
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next prev parent reply other threads:[~2013-03-20 17:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 16:09 Joel Brobecker
2013-03-20 16:14 ` Pedro Alves
2013-03-20 17:06 ` Jan Kratochvil
2013-03-20 17:08 ` Joel Sherrill [this message]
2013-03-20 17:20 ` Eli Zaretskii
2013-03-23 22:59 ` Eli Zaretskii
2013-03-24 0:01 ` Joel Brobecker
2013-03-24 0:07 ` Eli Zaretskii
2013-03-25 16:58 ` Joel Brobecker
2013-03-25 17:46 ` Eli Zaretskii
2013-03-25 18:10 ` Joel Brobecker
2013-03-29 8:02 ` Joel Brobecker
2013-03-29 14:03 ` Eli Zaretskii
2013-03-29 19:53 ` Joel Brobecker
2013-04-02 18:05 ` Eli Zaretskii
2013-04-05 13:03 ` Eli Zaretskii
2013-04-06 6:16 ` unbreak Windows hosted cross debugger builds (was: Re: one week to gdb-7.6 release?) Pedro Alves
2013-04-06 15:41 ` unbreak Windows hosted cross debugger builds " Eli Zaretskii
2013-03-29 15:23 ` one week to gdb-7.6 release? Ralf Corsepius
2013-03-29 16:42 ` m32r sim was " Joel Sherrill
2013-03-29 17:18 ` Mike Frysinger
2013-03-29 19:53 ` Joel Brobecker
2013-03-29 20:24 ` Joel Sherrill
2013-03-29 21:44 ` Joel Brobecker
2013-04-04 13:03 ` Ralf Corsepius
2013-04-10 15:01 ` Joel Brobecker
2013-03-25 19:08 ` Mark Kettenis
2013-03-25 19:12 ` Eli Zaretskii
2013-04-06 21:49 ` Pedro Alves
2013-04-07 3:58 ` Eli Zaretskii
2013-03-23 23:38 ` Joel Sherrill
2013-03-24 0:12 ` Mike Frysinger
2013-03-20 18:23 ` Ralf Corsepius
2013-04-01 19:56 ` Mike Frysinger
2013-03-29 12:53 Joel Sherrill
2013-03-29 14:15 ` Eli Zaretskii
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=5149EC84.7030008@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=ralf.corsepius@rtems.org \
--cc=vapier@gentoo.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