From: Pedro Alves <palves@redhat.com>
To: Doug Evans <xdje42@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Keith Seitz <keiths@redhat.com>
Subject: Re: gdb-7.8 branching status update
Date: Tue, 03 Jun 2014 08:32:00 -0000 [thread overview]
Message-ID: <538D8822.2030404@redhat.com> (raw)
In-Reply-To: <CAP9bCMR5qxFvqdbstu+6ZGhhVq8AK7uJb6sFzNqxZ398rEVsMQ@mail.gmail.com>
On 06/03/2014 09:22 AM, Doug Evans wrote:
> On Mon, Jun 2, 2014 at 10:47 AM, Pedro Alves <palves@redhat.com> wrote:
>> 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. :-/
>
> I'm not sure this is a blocker, but I've started to notice gdb segvs
> in corefile.exp.
> vdso target sections are not removed when a new core is loaded, and
> gdb is referencing memory from an already-freed bfd.
> At any rate I'm going to file a pr tomorrow.
That's sounds just like the break-interp.exp crashes mentioned above.
Markus followed up already (silly archives don't cross the month
boundary), but I haven't managed to reply yet, still busy with
the software step stuff.
--
Pedro Alves
next prev parent reply other threads:[~2014-06-03 8:32 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
2014-06-03 8:22 ` Doug Evans
2014-06-03 8:32 ` Pedro Alves [this message]
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=538D8822.2030404@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=xdje42@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).