From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 7.10 new branching date: Jun 29th, 2015
Date: Thu, 02 Jul 2015 17:18:00 -0000 [thread overview]
Message-ID: <20150702171839.GB3125@adacore.com> (raw)
In-Reply-To: <86si96o8si.fsf@gmail.com>
> When will we create the branch?
How about today? There was one pending item, but it got moved to
the "maybe" section of the 7.10 release TODO. So we should be good
to go.
I was really hoping that the patch issuing a warning when a discrepancy
between objfile being loaded in memory and actual executable being
debug is detected would make it... I'm wondering where we are at with
this one!
--
Joel
next prev parent reply other threads:[~2015-07-02 17:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 21:37 2 weeks to GDB 7.10 tentative branching date! Joel Brobecker
2015-06-02 8:12 ` Jan Kratochvil
2015-06-02 8:16 ` Phil Muldoon
2015-06-03 17:06 ` Joel Brobecker
2015-06-03 17:13 ` Jan Kratochvil
2015-06-03 17:32 ` Joel Brobecker
2015-06-03 19:01 ` GDB Bugzilla Target Milestone 7.10 [Re: 2 weeks to GDB 7.10 tentative branching date!] Jan Kratochvil
2015-06-02 16:21 ` 2 weeks to GDB 7.10 tentative branching date! Yao Qi
2015-06-02 16:33 ` Jan Kratochvil
2015-06-02 20:45 ` Philippe Waroquiers
2015-06-03 17:38 ` Joel Brobecker
2015-06-03 20:06 ` Philippe Waroquiers
2015-06-03 18:08 ` Doug Evans
2015-06-04 17:25 ` Doug Evans
2015-06-15 13:58 ` GDB 7.10 new branching date: Jun 29th, 2015 (was: "Re: 2 weeks to GDB 7.10 tentative branching date!") Joel Brobecker
2015-07-02 15:53 ` GDB 7.10 new branching date: Jun 29th, 2015 Yao Qi
2015-07-02 17:18 ` Joel Brobecker [this message]
2015-07-03 10:23 ` Gary Benson
2015-07-06 11:11 ` Yao Qi
2015-07-06 16:37 ` Joel Brobecker
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=20150702171839.GB3125@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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