Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: Andrew Cagney <ac131313@cygnus.com>,
	Michael Snyder <msnyder@cygnus.com>,
	gdb-patches@sources.redhat.com
Subject: Re: PATCH: resume + threads + software stepping == boom
Date: Sun, 10 Jun 2001 21:40:00 -0000	[thread overview]
Message-ID: <3B244B4B.4F8A@redhat.com> (raw)
In-Reply-To: <20010609160611.A26105@nevyn.them.org>

Daniel Jacobowitz wrote:
[extensive snipping]
> +  /* If we stopped on a breakpoint and it was not deleted, we want to continue
> +     only this thread, so we should be stepping. */

I agree with the premise -- whenever we resume at a breakpoint,
we should do a single-thread-step before inserting bps, so that 
other threads do not have a chance to run (and possibly go past
other breakpoints) while breakpoints are not inserted.

How do others feel about that premise?  I think we had 
reached that consensus at some earlier time, but it has not
been implemented (almost, but not quite).


  reply	other threads:[~2001-06-10 21:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08 12:34 Daniel Jacobowitz
2001-06-08 14:10 ` Daniel Jacobowitz
2001-06-08 16:19 ` Michael Snyder
2001-06-08 16:20   ` Michael Snyder
2001-06-08 16:43     ` Daniel Jacobowitz
     [not found]       ` <3B225994.9060502@cygnus.com>
2001-06-09 16:05         ` Daniel Jacobowitz
2001-06-10 21:40           ` Michael Snyder [this message]
2001-06-13 15:21           ` Michael Snyder
2001-06-09 13:34 ` Andrew Cagney
2001-06-09 15:44   ` Daniel Jacobowitz
2001-06-11 17:53     ` Jim Blandy

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=3B244B4B.4F8A@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=dmj+@andrew.cmu.edu \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@cygnus.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