From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Cc: keiths@redhat.com, dje@google.com
Subject: Re: gdb-7.8 branching status update
Date: Mon, 02 Jun 2014 17:47:00 -0000 [thread overview]
Message-ID: <538CB897.6050703@redhat.com> (raw)
In-Reply-To: <20140602172105.GC30686@adacore.com>
On 06/02/2014 06:21 PM, Joel Brobecker wrote:
> - infrun regression on platforms using software single step (Eg AIX).
> See PR gdb/17000. A patch was sent this past weekend, and is
> awaiting review.
I've been poking at this one all day long. I noticed something while
reviewing it, and then hit a stack of issues. I'll reply very soon.
I think the break-interp.exp crashes should be a blocker too:
https://sourceware.org/ml/gdb-patches/2014-05/msg00731.html
Also, I've now noticed that running the testsuite against
gdbserver has several regressions compared to a month or
so ago. :-/
--
Pedro Alves
next prev parent reply other threads:[~2014-06-02 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 17:21 Joel Brobecker
2014-06-02 17:47 ` Pedro Alves [this message]
2014-06-03 8:22 ` Doug Evans
2014-06-03 8:32 ` Pedro Alves
2014-06-03 8:36 ` Doug Evans
2014-06-03 13:43 ` 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=538CB897.6050703@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).