Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Maxim Grigoriev <maxim@tensilica.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Marc Gauthier <marc@tensilica.com>
Subject: Re: Faster stepping amidst breakpoints
Date: Mon, 31 Jan 2011 07:47:00 -0000	[thread overview]
Message-ID: <20110131044951.GG2384@adacore.com> (raw)
In-Reply-To: <20110123001433.GA6352@caradoc.them.org>

> Consider "set breakpoint always-inserted".
> I've been wondering lately if we should flip the default.

I like the idea of changing the default.

Do you know what the risks would be?  I looked at the code, and
there isn't something obvious/delicate, it seems.  Perhaps we might
find ourselves forgetting to re-insert breakpoints, or inserting
them twice? I think you guys have more experience than we do?

In terms of when, perhaps a good time to switch would be either
now (about 3 weeks away from planned 7.3 branching), or in 3 weeks
from now, right after branching.

-- 
Joel


  parent reply	other threads:[~2011-01-31  4:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22 15:06 Maxim Grigoriev
2011-01-24  8:04 ` Daniel Jacobowitz
2011-01-24 21:08   ` Maxim Grigoriev
2011-01-31  7:47   ` Joel Brobecker [this message]
2011-01-31 15:39     ` Daniel Jacobowitz
2011-02-01  3:23       ` Joel Brobecker
2011-02-01 18:44         ` Michael Snyder
2011-02-03  4:55           ` Joel Brobecker
2011-02-02 17:10         ` Daniel Jacobowitz
2011-02-03  4:46           ` Joel Brobecker
2011-02-13 15:17         ` Mark Kettenis
2011-02-14  3:27           ` Joel Brobecker
2011-02-14 10:50             ` Joel Brobecker
2011-02-01 15:12       ` Pedro Alves
2011-02-03 22:54     ` Maxim Grigoriev
2011-02-04 16:06       ` Tom Tromey
2011-02-04 19:32         ` Maxim Grigoriev
2011-02-04 16:33       ` Daniel Jacobowitz

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=20110131044951.GG2384@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc@tensilica.com \
    --cc=maxim@tensilica.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