Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org, sergiodj@redhat.com,
	Yao Qi <yao@codesourcery.com>, Pedro Alves <palves@redhat.com>,
	keiths@redhat.com
Subject: Re: RFC: branching for GDB 7.11 soon? (possibly Wed)
Date: Sun, 07 Feb 2016 08:12:00 -0000	[thread overview]
Message-ID: <20160207081230.GA20874@adacore.com> (raw)
In-Reply-To: <20160201030638.GG4008@adacore.com>

Hello again,

So, quick recap of where we are with respect to branching:

> PR19474 "break LINE_NUM" set breakpoint on file other than current source file

Analyzed, tricky to fix, not blocking for 7.11

> PR19503 internal-error: linux_nat_resume: Assertion `lp != NULL' failed.

Fixed by Pedro.

> 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 will try to take a look at them this weekend)

PR 19548 - breakpoint re-set inserts breakpoints when it shouldn't
Pedro sent a patch:
https://sourceware.org/ml/gdb-patches/2016-02/msg00014.html

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?

Sergio - would you be able to give us a rough description of how
good the results are in the buildbots? Anything we should be
aware of for this release? (Thanks!)

Thanks!
-- 
Joel


  parent reply	other threads:[~2016-02-07  8:12 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 ` Joel Brobecker [this message]
2016-02-08 18:03   ` RFC: branching for GDB 7.11 soon? (possibly Wed) 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
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=20160207081230.GA20874@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=palves@redhat.com \
    --cc=sergiodj@redhat.com \
    --cc=yao@codesourcery.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