From: Keith Seitz <keiths@redhat.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: RFC: branching for GDB 7.11 soon? (possibly Wed)
Date: Tue, 09 Feb 2016 22:37:00 -0000 [thread overview]
Message-ID: <56BA6A25.4080605@redhat.com> (raw)
In-Reply-To: <56B9DD81.5030606@redhat.com>
On 02/09/2016 04:37 AM, Pedro Alves wrote:
> On 02/09/2016 11:56 AM, Joel Brobecker wrote:
>> Hello everyone,
>>
>> Once again, I am very grateful to everyone who is so responsive
>> in trying to help us create that branch!
>>
>> Quick status update again, based on the latest feedback:
>>
>>>> PR19506 Regression with gdb.Breakpoint("*<addr>")
>>>
>>> This lead to a wider fix:
>>> [PATCH V2 0/4] Add support for "legacy" linespecs
>>> https://www.sourceware.org/ml/gdb-patches/2016-02/msg00024.html
>>
>> I took a look over the weekend, and it seems fairly unintrusive.
>> I propose we push it now. Otherwise, I think it's safe to create
>> the branch before pushing this patch, and backport afterwards.
>
> I took a quick look and it looks fine to me too.
Well, that's two global maintainers who think it looks okay; I've pushed
this.
>>> There is also a crash (regression):
>>>
>>> PR 19546 - gdb crash calling exec in the inferior
>>> Initial guestimate from Pedro:
>>> | Looks like a regression of the explicit locations work.
>>> Still in Pedro's court, or could Keith help?
>>
>> Looks like the fix is fairly straightforward.
>>
Patch submitted:
https://sourceware.org/ml/gdb-patches/2016-02/msg00245.html
Keith
next prev parent reply other threads:[~2016-02-09 22:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 3:06 Joel Brobecker
2016-02-01 13:34 ` Pedro Alves
2016-02-01 17:04 ` Pedro Alves
2016-02-01 19:51 ` Keith Seitz
2016-02-04 0:45 ` [RFC] breakpoints/19474 [was Re: RFC: branching for GDB 7.11 soon? (possibly Wed)] Keith Seitz
2016-02-04 1:33 ` Keith Seitz
2016-02-04 11:05 ` Yao Qi
2016-02-04 12:31 ` Pedro Alves
2016-08-12 12:00 ` Yao Qi
2016-02-07 8:12 ` RFC: branching for GDB 7.11 soon? (possibly Wed) Joel Brobecker
2016-02-08 18:03 ` Sergio Durigan Junior
2016-02-08 19:28 ` Keith Seitz
2016-02-08 20:06 ` Pedro Alves
2016-02-08 20:11 ` Keith Seitz
2016-02-09 5:35 ` Sergio Durigan Junior
2016-02-09 14:15 ` Simon Marchi
2016-02-09 14:18 ` Pedro Alves
2016-02-09 14:52 ` Simon Marchi
2016-02-09 18:31 ` Sergio Durigan Junior
2016-02-09 11:56 ` Joel Brobecker
2016-02-09 12:37 ` Pedro Alves
2016-02-09 22:37 ` Keith Seitz [this message]
2016-02-10 3:40 ` Joel Brobecker
2016-02-10 10:04 ` Pedro Alves
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=56BA6A25.4080605@redhat.com \
--to=keiths@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).