Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Keep breakpoints always inserted.
Date: Fri, 14 Mar 2008 20:22:00 -0000	[thread overview]
Message-ID: <200803142322.04240.vladimir@codesourcery.com> (raw)
In-Reply-To: <20080310210844.GB14908@caradoc.them.org>

On Tuesday 11 March 2008 00:08:44 Daniel Jacobowitz wrote:
> On Thu, Feb 28, 2008 at 05:17:13PM +0300, Vladimir Prus wrote:
> > 
> > This is hopefully final revision of my patch to keep
> > breakpoints always inserted, which is needed to support
> > non-stop mode. A new variable 'breakpoint always-inserted'
> > is introduced that enables this mode.  When enabled,
> > breakpoints are inserted into target immediately when created,
> > and they are not removed when we stop.
> > 
> > Compared to the previous version of this patch:
> > - The always-inserted mode is actually configurable
> > - In always-inserted mode, breakpoints are removed
> > from target on detach/disconnect.
> > 
> > OK?
> 
> This patch is OK, if you will add the missing pieces: a NEWS entry and
> documentation for the new command, and a testcase that enables
> always-inserted and verifies that it isn't a brick.

Hmm. I think the ideally, we'd run entire testsuite with this
mode enabled -- there are various corner cases. But then, we might
regress the not-always-inserted-breakpoints mode. Although the
potential for breakage is higher for always-inserted mode. I really
don't know how to ensure good coverage for both.

- Volodya


  reply	other threads:[~2008-03-14 20:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 14:18 Vladimir Prus
2008-03-10 21:09 ` Daniel Jacobowitz
2008-03-14 20:22   ` Vladimir Prus [this message]
2008-03-15 10:13   ` Vladimir Prus
2008-03-15 15:10     ` Eli Zaretskii
2008-04-02 13:02       ` Vladimir Prus
2008-04-02 18:18         ` Eli Zaretskii
2008-03-17 22:21     ` Daniel Jacobowitz
2008-03-18  4:15       ` Eli Zaretskii
2008-03-18  6:06         ` Vladimir Prus
2008-04-03 18:10       ` Vladimir Prus
2008-04-07 15:32         ` Daniel Jacobowitz
2008-04-09 23:45           ` Vladimir Prus
2008-04-10  8:16             ` Luis Machado
2008-04-17 16:50             ` Daniel Jacobowitz
2008-04-23 21:18               ` Pedro Alves
2008-04-23 21:24                 ` Daniel Jacobowitz
2008-04-24 11:22                   ` Vladimir Prus
2008-04-24 12:10                     ` Vladimir Prus

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=200803142322.04240.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.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